Dual Connectivity for Wireless Devices With Reduced Capabilities

ABSTRACT

A first base station may transmit, to a second base station, a secondary node addition request message. The secondary node addition request message may indicate: a secondary node addition request to allocate resources for dual connectivity operation; and that the secondary node addition request is for a wireless device of a reduced capability type. The reduced capability type may be associated with reduced capabilities compared to a non-reduced capability type. The first base station may receive, from the second base station, a secondary node addition request acknowledge message based on wireless devices of the reduced capability type being admitted by the second base station. The first base station may transmit, to the wireless device, configuration parameters of one or more cells of the second base station.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/160,268, filed Jan. 27, 2021, which claims the benefit of U.S. Provisional Application No. 62/967,013, filed Jan. 28, 2020, which is hereby incorporated by reference in its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A and FIG. 1B show examples of mobile communications systems in accordance with several of various embodiments of the present disclosure.

FIG. 2A and FIG. 2B show examples of user plane and control plane protocol layers in accordance with several of various embodiments of the present disclosure.

FIG. 3 shows example functions and services offered by protocol layers in a user plane protocol stack in accordance with several of various embodiments of the present disclosure.

FIG. 4 shows example flow of packets through the protocol layers in accordance with several of various embodiments of the present disclosure.

FIG. 5A shows example mapping of channels between layers of the protocol stack and different physical signals in downlink in accordance with several of various embodiments of the present disclosure.

FIG. 5B shows example mapping of channels between layers of the protocol stack and different physical signals in uplink in accordance with several of various embodiments of the present disclosure.

FIG. 6 shows example physical layer processes for signal transmission in accordance with several of various embodiments of the present disclosure.

FIG. 7 shows examples of RRC states and RRC state transitions in accordance with several of various embodiments of the present disclosure.

FIG. 8 shows an example time domain transmission structure in NR by grouping OFDM symbols into slots, subframes and frames in accordance with several of various embodiments of the present disclosure.

FIG. 9 shows an example of time-frequency resource grid in accordance with several of various embodiments of the present disclosure.

FIG. 10 shows example adaptation and switching of bandwidth parts in accordance with several of various embodiments of the present disclosure.

FIG. 11A shows example arrangements of carriers in carrier aggregation in accordance with several of various embodiments of the present disclosure.

FIG. 11B shows examples of uplink control channel groups in accordance with several of various embodiments of the present disclosure.

FIG. 12A, FIG. 12B and FIG. 12C show example random access processes in accordance with several of various embodiments of the present disclosure.

FIG. 13A shows example time and frequency structure of SSBs and their associations with beams in accordance with several of various embodiments of the present disclosure.

FIG. 13B shows example time and frequency structure of CSI-RSs and their association with beams in accordance with several of various embodiments of the present disclosure.

FIG. 14A, FIG. 14B and FIG. 14C show example beam management processes in accordance with several of various embodiments of the present disclosure.

FIG. 15 shows example components of a wireless device and a base station that are in communication via an air interface in accordance with several of various embodiments of the present disclosure.

FIG. 16A shows an example user plane protocol stack on the Xn interface in accordance with several of various embodiments of the present disclosure.

FIG. 16B shows an example control plane protocol stack of the Xn interface in accordance with several of various embodiments of the present disclosure.

FIG. 17 shows example components of an inter-gNB handover procedure in accordance with several of various embodiments of the present disclosure.

FIG. 18 shows an example handover scenario in accordance with several of various embodiments of the present disclosure.

FIG. 19 shows an example measurement process in accordance with several of various embodiments of the present disclosure.

FIG. 20 shows a handover preparation procedure in accordance with several of various embodiments of the present disclosure.

FIG. 21 shows example signaling for unsuccessful handover preparation in accordance with several of various embodiments of the present disclosure.

FIG. 22 shows an example handover cancel procedure in accordance with several of various embodiments of the present disclosure.

FIG. 23 shows an example S-NG-RAN node addition preparation procedure in accordance with several of various embodiments of the present disclosure.

FIG. 24 shows example signaling for unsuccessful S-NG-RAN node addition in accordance with several of various embodiments of the present disclosure.

FIG. 25 shows an example Xn Setup procedure in accordance with several of various embodiments of the present disclosure.

FIG. 26 shows an example process in accordance with several of various embodiments of the present disclosure.

FIG. 27 shows an example process in accordance with several of various embodiments of the present disclosure.

FIG. 28 shows an example process in accordance with several of various embodiments of the present disclosure.

FIG. 29 shows an example process in accordance with several of various embodiments of the present disclosure.

FIG. 30 shows an example process in accordance with several of various embodiments of the present disclosure.

FIG. 31 shows an example process in accordance with several of various embodiments of the present disclosure.

FIG. 32 shows an example handover process in accordance with several of various embodiments of the present disclosure.

FIG. 33 shows an example flow diagram in accordance with several of various embodiments of the present disclosure.

FIG. 34 shows an example flow diagram in accordance with several of various embodiments of the present disclosure.

FIG. 35 shows an example flow diagram in accordance with several of various embodiments of the present disclosure.

FIG. 36 shows an example flow diagram in accordance with several of various embodiments of the present disclosure.

FIG. 37 shows an example flow diagram in accordance with several of various embodiments of the present disclosure.

FIG. 38 shows an example flow diagram in accordance with several of various embodiments of the present disclosure.

FIG. 39 shows an example flow diagram in accordance with several of various embodiments of the present disclosure.

FIG. 40 shows an example flow diagram in accordance with several of various embodiments of the present disclosure.

DETAILED DESCRIPTION

The exemplary embodiments of the disclosed technology enable operation of a wireless device, including a wireless device with reduced capability, and/or one or more base stations. The exemplary disclosed embodiments may be implemented in the technical field of wireless communication systems. More particularly, the embodiment of the disclosed technology may enable wireless device and wireless network processes based on wireless device type.

The devices and/or nodes of the mobile communications system disclosed herein may be implemented based on various technologies and/or various releases/versions/amendments of a technology. The various technologies include various releases of long-term evolution (LTE) technologies, various releases of 5G new radio (NR) technologies, various wireless local area networks technologies and/or a combination thereof and/or alike. For example, a base station may support a given technology and may communicate with wireless devices with different characteristics. The wireless devices may have different categories that define their capabilities in terms of supporting various features. The wireless device with the same category may have different capabilities. The wireless devices may support various technologies such as various releases of LTE technologies, various releases of 5G NR technologies and/or a combination thereof and/or alike. At least some of the wireless devices in the mobile communications system of the present disclosure may be stationary or almost stationary. In this disclosure, the terms “mobile communications system” and “wireless communications system” may be used interchangeably.

FIG. 1A shows an example of a mobile communications system 100 in accordance with several of various embodiments of the present disclosure. The mobile communications system 100 may be, for example, run by a mobile network operator (MNO) or a mobile virtual network operator (MVNO). The mobile communications system 100 may be a public land mobile network (PLMN) run by a network operator providing a variety of service including voice, data, short messaging service (SMS), multimedia messaging service (MMS), emergency calls, etc. The mobile communications system 100 includes a core network (CN) 106, a radio access network (RAN) 104 and at least one wireless device 102.

The CN 106 connects the RAN 104 to one or more external networks (e.g., one or more data networks such as the Internet) and is responsible for functions such as authentication, charging and end-to-end connection establishment. Several radio access technologies (RATs) may be served by the same CN 106.

The RAN 104 may implement a RAT and may operate between the at least one wireless device 102 and the CN 106. The RAN 104 may handle radio related functionalities such as scheduling, radio resource control, modulation and coding, multi-antenna transmissions and retransmission protocols. The wireless device and the RAN may share a portion of the radio spectrum by separating transmissions from the wireless device to the RAN and the transmissions from the RAN to the wireless device. The direction of the transmissions from the wireless device to the RAN is known as the uplink and the direction of the transmissions from the RAN to the wireless device is known as the downlink. The separation of uplink and downlink transmissions may be achieved by employing a duplexing technique. Example duplexing techniques include frequency division duplexing (FDD), time division duplexing (TDD) or a combination of FDD and TDD.

In this disclosure, the term wireless device may refer to a device that communicates with a network entity or another device using wireless communication techniques. The wireless device may be a mobile device or a non-mobile (e.g., fixed) device. Examples of the wireless device include cellular phone, smart phone, tablet, laptop computer, wearable device (e.g., smart watch, smart shoe, fitness trackers, smart clothing, etc.), wireless sensor, wireless meter, extended reality (XR) devices including augmented reality (AR) and virtual reality (VR) devices, Internet of Things (IoT) device, vehicle to vehicle communications device, road-side units (RSU), automobile, relay node or any combination thereof. In some examples, the wireless device (e.g., a smart phone, tablet, etc.) may have an interface (e.g., a graphical user interface (GUI)) for configuration by an end user. In some examples, the wireless device (e.g., a wireless sensor device, etc.) may not have an interface for configuration by an end user. The wireless device may be referred to as a user equipment (UE), a mobile station (MS), a subscriber unit, a handset, an access terminal, a user terminal, a wireless transmit and receive unit (WTRU) and/or other terminology.

The at least one wireless device may communicate with at least one base station in the RAN 104. In this disclosure, the term base station may encompass terminologies associated with various RATs. For example, a base station may be referred to as a Node B in a 3G cellular system such as Universal Mobile Telecommunication Systems (UMTS), an evolved Node B (eNB) in a 4G cellular system such as evolved universal terrestrial radio access (E-UTRA), a next generation eNB (ng-eNB), a Next Generation Node B (gNB) in NR and/or a 5G system, an access point (AP) in Wi-Fi and/or other wireless local area networks. A base station may be referred to as a remote radio head (RRH), a baseband unit (BBU) in connection with one or more RRHs, a repeater or relay for coverage extension and/or any combination thereof. In some examples, all protocol layers of a base station may be implemented in one unit. In some example, some of the protocol layers (e.g., upper layers) of the base station may be implemented in a first unit (e.g., a central unit (CU)) and some other protocol layer (e.g., lower layers) may be implemented in one or more second units (e.g., distributed units (DUs)).

A base station in the RAN 104 includes one or more antennas to communicate with the at least one wireless device. The base station may communicate with the at least one wireless device using radio frequency (RF) transmissions and receptions via RF transceivers. The base station antennas may control one or more cells (or sectors). The size and/or radio coverage area of a cell may depend on the range that transmissions by a wireless device can be successfully received by the base station when the wireless device transmits using the RF frequency of the cell. The base station may be associated with cells of various sizes. At a given location, the wireless device may be in coverage area of a first cell of the base station and may not be in coverage area of a second cell of the base station depending on the sizes of the first cell and the second cell.

A base station in the RAN 104 may have various implementations. For example, a base station may be implemented by connecting a BBU (or a BBU pool) coupled to one or more RRHs and/or one or more relay nodes to extend the cell coverage. The BBU pool may be located at a centralized site like a cloud or data center. The BBU pool may be connected to a plurality of RRHs that control a plurality of cells. The combination of BBU with the one or more RRHs may be referred to as a centralized or cloud RAN (C-RAN) architecture. In some implementations, the BBU functions may be implemented on virtual machines (VMs) on servers at a centralized location. This architecture may be referred to as virtual RAN (vRAN). All, most or a portion of the protocol layer functions (e.g., all or portions of physical layer, medium access control (MAC) layer and/or higher layers) may be implemented at the BBU pool and the processed data may be transmitted to the RRHs for further processing and/or RF transmission. The links between the BBU pool and the RRHs may be referred to as fronthaul.

In some deployment scenarios, the RAN 104 may include macrocell base stations with high transmission power levels and large coverage areas. In other deployment scenarios, the RAN 104 may include base stations that employ different transmission power levels and/or have cells with different coverage areas. For example, some base station may be macrocell base stations with high transmission powers and/or large coverage areas and other base station may be small cell base stations with comparatively smaller transmission powers and/or coverage areas. In some deployment scenarios, a small cell base station may have coverage that is within or has overlap with coverage area of a macrocell base station. A wireless device may communicate with the macrocell base station while within the coverage area of the macrocell base station. For additional capacity, the wireless device may communicate with both the macrocell base station and the small cell base station while in the overlapped coverage area of the macrocell base station and the small cell base station. Depending on their coverage areas, a small cell base station may be referred to as a microcell base station, a picocell base station, a femtocell base station or a home base station.

Different standard development organizations (SDOs) have specified, or may specify in future, mobile communications systems that have similar characteristics as the mobile communications system 100 of FIG. 1A. For example, the Third-Generation Partnership Project (3GPP) is a group of SDOs that provides specifications that define 3GPP technologies for mobile communications systems that are akin to the mobile communications system 100. The 3GPP has developed specifications for third generation (3G) mobile networks, fourth generation (4G) mobile networks and fifth generation (5G) mobile networks. The 3G, 4G and 5G networks are also known as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE) and 5G system (5GS), respectively. In this disclosure, embodiments are described with respect to the RAN implemented in a 3GPP 5G mobile network that is also referred to as next generation RAN (NG-RAN). The embodiments may also be implemented in other mobile communications systems such as 3G or 4G mobile networks or mobile networks that may be standardized in future such as sixth generation (6G) mobile networks or mobile networks that are implemented by standards bodies other than 3GPP. The NG-RAN may be based on a new RAT known as new radio (NR) and/or other radio access technologies such as LTE and/or non-3GPP RATs.

FIG. 1B shows an example of a mobile communications system 110 in accordance with several of various embodiments of the present disclosure. The mobile communications system 110 of FIG. 1B is an example of a 5G mobile network and includes a 5G CN (5G-CN) 130, an NG-RAN 120 and UEs (collectively 112 and individually UE 112A and UE 112B). The 5G-CN 130, the NG-RAN 120 and the UEs 112 of FIG. 1B operate substantially alike the CN 106, the RAN 104 and the at least one wireless device 102, respectively, as described for FIG. 1A.

The 5G-CN 130 of FIG. 1B connects the NG-RAN 120 to one or more external networks (e.g., one or more data networks such as the Internet) and is responsible for functions such as authentication, charging and end-to-end connection establishment. The 5G-CN has new enhancements compared to previous generations of CNs (e.g., evolved packet core (EPC) in the 4G networks) including service-based architecture, support for network slicing and control plane/user plane split. The service-based architecture of the 5G-CN provides a modular framework based on service and functionalities provided by the core network wherein a set of network functions are connected via service-based interfaces. The network slicing enables multiplexing of independent logical networks (e.g., network slices) on the same physical network infrastructure. For example, a network slice may be for mobile broadband applications with full mobility support and a different network slice may be for non-mobile latency-critical applications such as industry automation. The control plane/user plane split enables independent scaling of the control plane and the user plane. For example, the control plane capacity may be increased without affecting the user plane of the network.

The 5G-CN 130 of FIG. 1B includes an access and mobility management function (AMF) 132 and a user plane function (UPF) 134. The AMF 132 may support termination of non-access stratum (NAS) signaling, NAS signaling security such as ciphering and integrity protection, inter-3GPP access network mobility, registration management, connection management, mobility management, access authentication and authorization and security context management. The NAS is a functional layer between a UE and the CN and the access stratum (AS) is a functional layer between the UE and the RAN. The UPF 134 may serve as an interconnect point between the NG-RAN and an external data network. The UPF may support packet routing and forwarding, packet inspection and Quality of Service (QoS) handling and packet filtering. The UPF may further act as a Protocol Data Unit (PDU) session anchor point for mobility within and between RATs.

The 5G-CN 130 may include additional network functions (not shown in FIG. 1B) such as one or more Session Management Functions (SMFs), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and/or an Authentication Server Function (AUSF). These network functions along with the AMF 132 and UPF 134 enable a service-based architecture for the 5G-CN.

The NG-RAN 120 may operate between the UEs 112 and the 5G-CN 130 and may implement one or more RATs. The NG-RAN 120 may include one or more gNBs (e.g., gNB 122A or gNB 122B or collectively gNBs 122) and/or one or more ng-eNBs (e.g., ng-eNB 124A or ng-eNB 124B or collectively ng-eNB s 124). The general terminology for gNB s 122 and/or an ng-eNBs 124 is a base station and may be used interchangeably in this disclosure. The gNBs 122 and the ng-eNBs 124 may include one or more antennas to communicate with the UEs 112. The one or more antennas of the gNB s 122 or ng-eNBs 124 may control one or more cells (or sectors) that provide radio coverage for the UEs 112.

A gNB and/or an ng-eNB of FIG. 1B may be connected to the 5G-CN 130 using an NG interface. A gNB and/or an ng-eNB may be connected with other gNBs and/or ng-eNBs using an Xn interface. The NG or the Xn interfaces are logical connections that may be established using an underlying transport network. The interface between a UE and a gNB or between a UE and an ng-eNBs may be referred to as the Uu interface. An interface (e.g., Uu, NG or Xn) may be established by using a protocol stack that enables data and control signaling exchange between entities in the mobile communications system of FIG. 1B. When a protocol stack is used for transmission of user data, the protocol stack may be referred to as user plane protocol stack. When a protocol stack is used for transmission of control signaling, the protocol stack may be referred to as control plane protocol stack. Some protocol layer may be used in both of the user plane protocol stack and the control plane protocol stack while other protocol layers may be specific to the user plane or control plane.

The NG interface of FIG. 1B may include an NG-User plane (NG-U) interface between a gNB and the UPF 134 (or an ng-eNB and the UPF 134) and an NG-Control plane (NG-C) interface between a gNB and the AMF 132 (or an ng-eNB and the AMF 132). The NG-U interface may provide non-guaranteed delivery of user plane PDUs between a gNB and the UPF or an ng-eNB and the UPF. The NG-C interface may provide services such as NG interface management, UE context management, UE mobility management, transport of NAS messages, paging, PDU session management, configuration transfer and/or warning message transmission.

The UEs 112 and a gNB may be connected using the Uu interface and using the NR user plane and control plane protocol stack. The UEs 112 and an ng-eNB may be connected using the Uu interface using the LTE user plane and control plane protocol stack.

In the example mobile communications system of FIG. 1B, a 5G-CN is connected to a RAN comprised of 4G LTE and/or 5G NR RATs. In other example mobile communications systems, a RAN based on the 5G NR RAT may be connected to a 4G CN (e.g., EPC). For example, earlier releases of 5G standards may support a non-standalone mode of operation where a NR based RAN is connected to the 4G EPC. In an example non-standalone mode, a UE may be connected to both a 5G NR gNB and a 4G LTE eNB (e.g., a ng-eNB) and the control plane functionalities (such as initial access, paging and mobility) may be provided through the 4G LTE eNB. In a standalone of operation, the 5G NR gNB is connected to a 5G-CN and the user plane and the control plane functionalities are provided by the 5G NR gNB.

FIG. 2A shows an example of the protocol stack for the user plan of an NR Uu interface in accordance with several of various embodiments of the present disclosure. The user plane protocol stack comprises five protocol layers that terminate at the UE 200 and the gNB 210. The five protocol layers, as shown in FIG. 2A, include physical (PHY) layer referred to as PHY 201 at the UE 200 and PHY 211 at the gNB 210, medium access control (MAC) layer referred to as MAC 202 at the UE 200 and MAC 212 at the gNB 210, radio link control (RLC) layer referred to as RLC 203 at the UE 200 and RLC 213 at the gNB 210, packet data convergence protocol (PDCP) layer referred to as PDCP 204 at the UE 200 and PDCP 214 at the gNB 210, and service data application protocol (SDAP) layer referred to as SDAP 205 at the UE 200 and SDAP 215 at the gNB 210. The PHY layer, also known as layer 1 (L1), offers transport services to higher layers. The other four layers of the protocol stack (MAC, RLC, PDCP and SDAP) are collectively known as layer 2 (L2).

FIG. 2B shows an example of the protocol stack for the control plan of an NR Uu interface in accordance with several of various embodiments of the present disclosure. Some of the protocol layers (PHY, MAC, RLC and PDCP) are common between the user plane protocol stack shown in FIG. 2A and the control plan protocol stack. The control plane protocol stack also includes the RRC layer, referred to RRC 206 at the UE 200 and RRC 216 at the gNB 210, that also terminates at the UE 200 and the gNB 210. In addition, the control plane protocol stack includes the NAS layer that terminates at the UE 200 and the AMF 220. In FIG. 2B, the NAS layer is referred to as NAS 207 at the UE 200 and NAS 227 at the AMF 220.

FIG. 3 shows example functions and services offered to other layers by a layer in the NR user plane protocol stack of FIG. 2A in accordance with several of various embodiments of the present disclosure. For example, the SDAP layer of FIG. 3 (shown in FIG. 2A as SDAP 205 at the UE side and SDAP 215 at the gNB side) may perform mapping and de-mapping of QoS flows to data radio bearers. The mapping and de-mapping may be based on QoS (e.g., delay, throughput, jitter, error rate, etc.) associated with a QoS flow. A QoS flow may be a QoS differentiation granularity for a PDU session which is a logical connection between a UE 200 and a data network. A PDU session may contain one or more QoS flows. The functions and services of the SDAP layer include mapping and de-mapping between one or more QoS flows and one or more data radio bearers. The SDAP layer may also mark the uplink and/or downlink packets with a QoS flow ID (QFI).

The PDCP layer of FIG. 3 (shown in FIG. 2A as PDCP 204 at the UE side and PDCP 214 at the gNB side) may perform header compression and decompression (e.g., using Robust Header Compression (ROHC) protocol) to reduce the protocol header overhead, ciphering and deciphering and integrity protection and verification to enhance the security over the air interface, reordering and in-order delivery of packets and discarding of duplicate packets. A UE may be configured with one PDCP entity per bearer.

In an example scenario not shown in FIG. 3, a UE may be configured with dual connectivity and may connect to two different cell groups provided by two different base stations. For example, a base station of the two base stations may be referred to as a master base station and a cell group provided by the master base station may be referred to as a master cell group (MCG). The other base station of the two base stations may be referred to as a secondary base station and the cell group provided by the secondary base station may be referred to as a secondary cell group (SCG). A bearer may be configured for the UE as a split bearer that may be handled by the two different cell groups. The PDCP layer may perform routing of packets corresponding to a split bearer to and/or from RLC channels associated with the cell groups.

In an example scenario not shown in FIG. 3, a bearer of the UE may be configured (e.g., with control signaling) with PDCP packet duplication. A bearer configured with PDCP duplication may be mapped to a plurality of RLC channels each corresponding to different one or more cells. The PDCP layer may duplicate packets of the bearer configured with PDCP duplication and the duplicated packets may be mapped to the different RLC channels. With PDCP packet duplication, the likelihood of correct reception of packets increases thereby enabling higher reliability.

The RLC layer of FIG. 3 (shown in FIG. 2A as RLC 203 at the UE side and RLC 213 at the gNB side) provides service to upper layers in the form of RLC channels. The RLC layer may include three transmission modes: transparent mode (TM), Unacknowledged mode (UM) and Acknowledged mode (AM). The RLC layer may perform error correction through automatic repeat request (ARQ) for the AM transmission mode, segmentation of RLC service data units (SDUs) for the AM and UM transmission modes and re-segmentation of RLC SDUs for AM transmission mode, duplicate detection for the AM transmission mode, RLC SDU discard for the AM and UM transmission modes, etc. The UE may be configured with one RLC entity per RLC channel.

The MAC layer of FIG. 3 (shown in FIG. 2A as MAC 202 at the UE side and MAC 212 at the gNB side) provides services to the RLC layer in form of logical channels. The MAC layer may perform mapping between logical channels and transport channels, multiplexing/demultiplexing of MAC SDUs belonging to one or more logical channels into/from transport blocks (TB s) delivered to/from the physical layer on transport channels, reporting of scheduling information, error correction through hybrid automatic repeat request (HARQ), priority handling between UEs by means of dynamic scheduling, priority handling between logical channels of one UE by means of logical channel prioritization and/or padding. In case of carrier aggregation, a MAC entity may comprise one HARQ entity per cell. A MAC entity may support multiple numerologies, transmission timings and cells. The control signaling may configure logical channels with mapping restrictions. The mapping restrictions in logical channel prioritization may control the numerology(ies), cell(s), and/or transmission timing(s)/duration(s) that a logical channel may use.

The PHY layer of FIG. 3 (shown in FIG. 2A as PHY 201 at the UE side and PHY 211 at the gNB side) provides transport services to the MAC layer in form of transport channels. The physical layer may handle coding/decoding, HARQ soft combining, rate matching of a coded transport channel to physical channels, mapping of coded transport channels to physical channels, modulation and demodulation of physical channels, frequency and time synchronization, radio characteristics measurements and indication to higher layers, RF processing, and mapping to antennas and radio resources.

FIG. 4 shows example processing of packets at different protocol layers in accordance with several of various embodiments of the present disclosure. In this example, three Internet Protocol (IP) packets that are processed by the different layers of the NR protocol stack. The term SDU shown in FIG. 4 is the data unit that is entered from/to a higher layer. In contrast, a protocol data unit (PDU) is the data unit that is entered to/from a lower layer. The flow of packets in FIG. 4 is for downlink. An uplink data flow through layers of the NR protocol stack is similar to FIG. 4. In this example, the two leftmost IP packets are mapped by the SDAP layer (shown as SDAP 205 and SDAP 215 in FIG. 2A) to radio bearer 402 and the rightmost packet is mapped by the SDAP layer to the radio bearer 404. The SDAP layer adds SDAP headers to the IP packets which are entered into the PDCP layer as PDCP SDUs. The PDCP layer is shown as PDCP 204 and PDCP 214 in FIG. 2A. The PDCP layer adds the PDCP headers to the PDCP SDUs which are entered into the RLC layer as RLC SDUs. The RLC layer is shown as RLC 203 and RLC 213 in FIG. 2A. An RLC SDU may be segmented at the RLC layer. The RLC layer adds RLC headers to the RLC SDUs after segmentation (if segmented) which are entered into the MAC layer as MAC SDUs. The MAC layer adds the MAC headers to the MAC SDUs and multiplexes one or more MAC SDUs to form a PHY SDU (also referred to as a transport block (TB) or a MAC PDU).

In FIG. 4, the MAC SDUs are multiplexed to form a transport block. The MAC layer may multiplex one or more MAC control elements (MAC CEs) with zero or more MAC SDUs to form a transport block. The MAC CEs may also be referred to as MAC commands or MAC layer control signaling and may be used for in-band control signaling. The MAC CEs may be transmitted by a base station to a UE (e.g., downlink MAC CEs) or by a UE to a base station (e.g., uplink MAC CEs). The MAC CEs may be used for transmission of information useful by a gNB for scheduling (e.g., buffer status report (BSR) or power headroom report (PHR)), activation/deactivation of one or more cells, activation/deactivation of configured radio resources for or one or more processes, activation/deactivation of one or more processes, indication of parameters used in one or more processes, etc.

FIG. 5A and FIG. 5B show example mapping between logical channels, transport channels and physical channels for downlink and uplink, respectively in accordance with several of various embodiments of the present disclosure. As discussed before, the MAC layer provides services to higher layer in the form of logical channels. A logical channel may be classified as a control channel, if used for transmission of control and/or configuration information, or a traffic channel if used for transmission of user data. Example logical channels in NR include Broadcast Control Channel (BCCH) used for transmission of broadcast system control information, Paging Control Channel (PCCH) used for carrying paging messages for wireless devices with unknown locations, Common Control Channel (CCCH) used for transmission of control information between UEs and network and for UEs that have no RRC connection with the network, Dedicated Control Channel (DCCH) which is a point-to-point bi-directional channel for transmission of dedicated control information between a UE that has an RRC connection and the network and Dedicated Traffic Channel (DTCH) which is point-to-point channel, dedicated to one UE, for the transfer of user information and may exist in both uplink and downlink.

As discussed before, the PHY layer provides services to the MAC layer and higher layers in the form of transport channels. Example transport channels in NR include Broadcast Channel (BCH) used for transmission of part of the BCCH referred to as master information block (MIB), Downlink Shared Channel (DL-SCH) used for transmission of data (e.g., from DTCH in downlink) and various control information (e.g., from DCCH and CCCH in downlink and part of the BCCH that is not mapped to the BCH), Uplink Shared Channel (UL-SCH) used for transmission of uplink data (e.g., from DTCH in uplink) and control information (e.g., from CCCH and DCCH in uplink) and Paging Channel (PCH) used for transmission of paging information from the PCCH. In addition, Random Access Channel (RACH) is a transport channel used for transmission of random access preambles. The RACH does not carry a transport block. Data on a transport channel (except RACH) may be organized in transport blocks, wherein One or more transport blocks may be transmitted in a transmission time interval (TTI).

The PHY layer may map the transport channels to physical channels. A physical channel may correspond to time-frequency resources that are used for transmission of information from one or more transport channels. In addition to mapping transport channels to physical channels, the physical layer may generate control information (e.g., downlink control information (DCI) or uplink control information (UCI)) that may be carried by the physical channels. Example DCI include scheduling information (e.g., downlink assignments and uplink grants), request for channel state information report, power control command, etc. Example UCI include HARQ feedback indicating correct or incorrect reception of downlink transport blocks, channel state information report, scheduling request, etc. Example physical channels in NR include a Physical Broadcast Channel (PBCH) for carrying information from the BCH, a Physical Downlink Shared Channel (PDSCH) for carrying information form the PCH and the DL-SCH, a Physical Downlink Control Channel (PDCCH) for carrying DCI, a Physical Uplink Shared Channel (PUSCH) for carrying information from the UL-SCH and/or UCI, a Physical Uplink Control Channel (PUCCH) for carrying UCI and Physical Random Access Channel (PRACH) for transmission of RACH (e.g., random access preamble).

The PHY layer may also generate physical signals that are not originated from higher layers. As shown in FIG. 5A, example downlink physical signals include Demodulation Reference Signal (DM-RS), Phase Tracking Reference Signal (PT-RS), Channel State Information Reference Signal (CSI-RS), Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS). As shown in FIG. 5B, example uplink physical signals include DM-RS, PT-RS and sounding reference signal (SRS).

As indicated earlier, some of the protocol layers (PHY, MAC, RLC and PDCP) of the control plane of an NR Uu interface, are common between the user plane protocol stack (as shown in FIG. 2A) and the control plane protocol stack (as shown in FIG. 2B). In addition to PHY, MAC, RLC and PDCP, the control plane protocol stack includes the RRC protocol layer and the NAS protocol layer.

The NAS layer, as shown in FIG. 2B, terminates at the UE 200 and the AMF 220 entity of the 5G-C 130. The NAS layer is used for core network related functions and signaling including registration, authentication, location update and session management. The NAS layer uses services from the AS of the Uu interface to transmit the NAS messages.

The RRC layer, as shown in FIG. 2B, operates between the UE 200 and the gNB 210 (more generally NG-RAN 120) and may provide services and functions such as broadcast of system information (SI) related to AS and NAS as well as paging initiated by the 5G-C 130 or NG-RAN 120. In addition, the RRC layer is responsible for establishment, maintenance and release of an RRC connection between the UE 200 and the NG-RAN 120, carrier aggregation configuration (e.g., addition, modification and release), dual connectivity configuration (e.g., addition, modification and release), security related functions, radio bearer configuration/maintenance and release, mobility management (e.g., maintenance and context transfer), UE cell selection and reselection, inter-RAT mobility, QoS management functions, UE measurement reporting and control, radio link failure (RLF) detection and NAS message transfer. The RRC layer uses services from PHY, MAC, RLC and PDCP layers to transmit RRC messages using signaling radio bearers (SRBs). The SRBs are mapped to CCCH logical channel during connection establishment and to DCCH logical channel after connection establishment.

FIG. 6 shows example physical layer processes for signal transmission in accordance with several of various embodiments of the present disclosure. Data and/or control streams from MAC layer may be encoded/decoded to offer transport and control services over the radio transmission link. For example, one or more (e.g., two as shown in FIG. 6) transport blocks may be received from the MAC layer for transmission via a physical channel (e.g., a physical downlink shared channel or a physical uplink shared channel). A cyclic redundancy check (CRC) may be calculated and attached to a transport block in the physical layer. The CRC calculation may be based on one or more cyclic generator polynomials. The CRC may be used by the receiver for error detection. Following the transport block CRC attachment, a low-density parity check (LDPC) base graph selection may be performed. In example embodiments, two LDPC base graphs may be used wherein a first LDPC base graph may be optimized for small transport blocks and a second LDPC base graph may be optimized for comparatively larger transport blocks.

The transport block may be segmented into code blocks and code block CRC may be calculated and attached to a code block. A code block may be LDPC coded and the LDPC coded blocks may be individually rate matched. The code blocks may be concatenated to create one or more codewords. The contents of a codeword may be scrambled and modulated to generate a block of complex-valued modulation symbols. The modulation symbols may be mapped to a plurality of transmission layers (e.g., multiple-input multiple-output (MIMO) layers) and the transmission layers may be subject to transform precoding and/or precoding. The precoded complex-valued symbols may be mapped to radio resources (e.g., resource elements). The signal generator block may create a baseband signal and up-convert the baseband signal to a carrier frequency for transmission via antenna ports. The signal generator block may employ mixers, filters and/or other radio frequency (RF) components prior to transmission via the antennas. The functions and blocks in FIG. 6 are illustrated as examples and other mechanisms may be implemented in various embodiments.

FIG. 7 shows examples of RRC states and RRC state transitions at a UE in accordance with several of various embodiments of the present disclosure. A UE may be in one of three RRC states: RRC_IDLE 702, RRC INACTIVE 704 and RRC_CONNECTED 706. In RRC_IDLE 702 state, no RRC context (e.g., parameters needed for communications between the UE and the network) may be established for the UE in the RAN. In RRC_IDLE 702 state, no data transfer between the UE and the network may take place and uplink synchronization is not maintained. The wireless device may sleep most of the time and may wake up periodically to receive paging messages. The uplink transmission of the UE may be based on a random access process and to enable transition to the RRC_CONNECTED 706 state. The mobility in RRC_IDLE 702 state is through a cell reselection procedure where the UE camps on a cell based on one or more criteria including signal strength that is determined based on the UE measurements.

In RRC_CONNECTED 706 state, the RRC context is established and both the UE and the RAN have necessary parameters to enable communications between the UE and the network. In the RRC_CONNECTED 706 state, the UE is configured with an identity known as a Cell Radio Network Temporary Identifier (C-RNTI) that is used for signaling purposes (e.g., uplink and downlink scheduling, etc.) between the UE and the RAN. The wireless device mobility in the RRC_CONNECTED 706 state is managed by the RAN. The wireless device provides neighboring cells and/or current serving cell measurements to the network and the network may make hand over decisions. Based on the wireless device measurements, the current serving base station may send a handover request message to a neighboring base station and may send a handover command to the wireless device to handover to a cell of the neighboring base station. The transition of the wireless device from the RRC_IDLE 702 state to the RRC_CONNECTED 706 state or from the RRC_CONNECTED 706 state to the RRC_IDLE 702 state may be based on connection establishment and connection release procedures (shown collectively as connection establishment/release 710 in FIG. 7).

To enable a faster transition to the RRC_CONNECTED 706 state (e.g., compared to transition from RRC_IDLE 702 state to RRC_CONNECTED 706 state), an RRC_INACTIVE 704 state is used for an NR UE wherein, the RRC context is kept at the UE and the RAN. The transition from the RRC_INACTIVE 704 state to the RRC_CONNECTED 706 state is handled by RAN without CN signaling. Similar to the RRC_IDLE 702 state, the mobility in RRC_INACTIVE 704 state is based on a cell reselection procedure without involvement from the network. The transition of the wireless device from the RRC_INACTIVE 704 state to the RRC_CONNECTED 706 state or from the RRC_CONNECTED 706 state to the RRC_INACTIVE 704 state may be based on connection resume and connection inactivation procedures (shown collectively as connection resume/inactivation 712 in FIG. 7). The transition of the wireless device from the RRC_INACTIVE 704 state to the RRC_IDLE 702 state may be based on a connection release 714 procedure as shown in FIG. 7.

In NR, Orthogonal Frequency Division Multiplexing (OFDM), also called cyclic prefix OFDM (CP-OFDM), is the baseline transmission scheme in both downlink and uplink of NR and the Discrete Fourier Transform (DFT) spread OFDM (DFT-s-OFDM) is a complementary uplink transmission in addition to the baseline OFDM scheme. OFDM is multi-carrier transmission scheme wherein the transmission bandwidth may be composed of several narrowband sub-carriers. The subcarriers are modulated by the complex valued OFDM modulation symbols resulting in an OFDM signal. The complex valued OFDM modulation symbols are obtained by mapping, by a modulation mapper, the input data (e.g., binary digits) to different points of a modulation constellation diagram. The modulation constellation diagram depends on the modulation scheme. NR may use different types of modulation schemes including Binary Phase Shift Keying (BPSK), n/2-BPSK, Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (16QAM), 64QAM and 256QAM. Different and/or higher order modulation schemes (e.g., M-QAM in general) may be used. An OFDM signal with N subcarriers may be generated by processing N subcarriers in parallel for example by using Inverse Fast Fourier Transform (IFFT) processing. The OFDM receiver may use FFT processing to recover the transmitted OFDM modulation symbols. The subcarrier spacing of subcarriers in an OFDM signal is inversely proportional to an OFDM modulation symbol duration. For example, for a 15 KHz subcarrier spacing, duration of an OFDM signal is nearly 66.7 μs. To enhance the robustness of OFDM transmission in time dispersive channels, a cyclic prefix (CP) may be inserted at the beginning of an OFDM symbol. For example, the last part of an OFDM symbol may be copied and inserted at the beginning of an OFDM symbol. The CP insertion enhanced the OFDM transmission scheme by preserving subcarrier orthogonality in time dispersive channels.

In NR, different numerologies may be used for OFDM transmission. A numerology of OFDM transmission may indicate a subcarrier spacing and a CP duration for the OFDM transmission. For example, a subcarrier spacing in NR may generally be a multiple of 15 KHz and expressed as Δf=2^(μ)·15 KHz (μ=0, 1, 2, . . . ). Example subcarrier spacings used in NR include 15 KHz (μ=0), 30 KHz (μ=1), 60 KHz (μ=2), 120 KHz (μ=3) and 240 KHz (μ=4). As discussed before, a duration of OFDM symbol is inversely proportional to the subcarrier spacing and therefor OFDM symbol duration may depend on the numerology (e.g. the μ value).

FIG. 8 shows an example time domain transmission structure in NR wherein OFDM symbols are grouped into slots, subframes and frames in accordance with several of various embodiments of the present disclosure. A slot is a group of N_(symb) ^(slot) OFDM symbols, wherein the N_(symb) ^(slot) may have a constant value (e.g., 14). Since different numerologies results in different OFDM symbol durations, duration of a slot may also depend on the numerology and may be variable. A subframe may have a duration of 1 ms and may be composed of one or more slots, the number of which may depend on the slot duration. The number of slots per subframe is therefore a function of μ and may generally expressed as N_(slot) ^(frame,μ) and the number of symbols per subframe may be expressed as N_(symb) ^(subframe,μ)=N_(symb) ^(slot)N_(slot) ^(subframe,μ). A frame may have a duration of 10 ms and may consist of 10 subframes. The number of slots per frame may depend on the numerology and therefore may be variable. The number of slots per frame may generally be expressed as N_(slot) ^(frame,μ).

An antenna port may be defined as a logical entity such that channel characteristics over which a symbol on the antenna port is conveyed may be inferred from the channel characteristics over which another symbol on the same antenna port is conveyed. For example, for DM-RS associated with a PDSCH, the channel over which a PDSCH symbol on an antenna port is conveyed may be inferred from the channel over which a DM-RS symbol on the same antenna port is conveyed, for example, if the two symbols are within the same resource as the scheduled PDSCH and/or in the same slot and/or in the same precoding resource block group (PRG). For example, for DM-RS associated with a PDCCH, the channel over which a PDCCH symbol on an antenna port is conveyed may be inferred from the channel over which a DM-RS symbol on the same antenna port is conveyed if, for example, the two symbols are within resources for which the UE may assume the same precoding being used. For example, for DM-RS associated with a PBCH, the channel over which a PBCH symbol on one antenna port is conveyed may be inferred from the channel over which a DM-RS symbol on the same antenna port is conveyed if, for example, the two symbols are within a SS/PBCH block transmitted within the same slot, and with the same block index. The antenna port may be different from a physical antenna. An antenna port may be associated with an antenna port number and different physical channels may correspond to different ranges of antenna port numbers.

FIG. 9 shows an example of time-frequency resource grid in accordance with several of various embodiments of the present disclosure. The number of subcarriers in a carrier bandwidth may be based on the numerology of OFDM transmissions in the carrier. A resource element, corresponding to one symbol duration and one subcarrier, may be the smallest physical resource in the time-frequency grid. A resource element (RE) for antenna port p and subcarrier spacing configuration μ may be uniquely identified by (k,l)_(p,μ) where k is the index of a subcarrier in the frequency domain and 1 may refer to the symbol position in the time domain relative to some reference point. A resource block may be defined as N_(SC) ^(RB)=12 subcarriers. Since subcarrier spacing depends on the numerology of OFDM transmission, the frequency domain span of a resource block may be variable and may depend on the numerology. For example, for a subcarrier spacing of 15 KHz (e.g., μ=0), a resource block may be 180 KHz and for a subcarrier spacing of 30 KHz (e.g., μ=1), a resource block may be 360 KHz.

With large carrier bandwidths defined in NR and due to limited capabilities for some UEs (e.g., due to hardware limitations), a UE may not support an entire carrier bandwidth. Receiving on the full carrier bandwidth may imply high energy consumption. For example, transmitting downlink control channels on the full downlink carrier bandwidth may result in high power consumption for wide carrier bandwidths. NR may use a bandwidth adaptation procedure to dynamically adapt the transmit and receive bandwidths. The transmit and receive bandwidth of a UE on a cell may be smaller than the bandwidth of the cell and may be adjusted. For example, the width of the transmit and/or receive bandwidth may change (e.g., shrink during period of low activity to save power); the location of the transmit and/or receive bandwidth may move in the frequency domain (e.g., to increase scheduling flexibility); and the subcarrier spacing of the transmit or receive bandwidth may change (e.g., to allow different services). A subset of the cell bandwidth may be referred to as a Bandwidth Part (BWP) and bandwidth adaptation may be achieved by configuring the UE with one or more BWPs. The base station may configure a UE with a set of downlink BWPs and a set of uplink BWPs. A BWP may be characterized by a numerology (e.g., subcarrier spacing and cyclic prefix) and a set of consecutive resource blocks in the numerology of the BWP. One or more first BWPs of the one or more BWPs of the cell may be active at a time. An active BWP may be an active downlink BWP or an active uplink BWP.

FIG. 10 shows an example of bandwidth part adaptation and switching. In this example, three BWPs (BWP₁ 1004, BWP₂ 1006 and BWP₃ 1008) are configured for a UE on a carrier bandwidth. The BWP₁ is configured with a bandwidth of 40 MHz and a numerology with subcarrier spacing of 15 KHz, the BWP₂ is configured with a bandwidth of 10 MHz and a numerology with subcarrier spacing of 15 KHz and the BWP₃ is configured with a bandwidth of 20 MHz and a subcarrier spacing of 60 KHz. The wireless device may switch from a first BWP (e.g., BWP₁) to a second BWP (e.g., BWP₂). An active BWP of the cell may change from the first BWP to the second BWP in response to the BWP switching.

The BWP switching (e.g., BWP switching 1010, BWP switching 1012, BWP switching 1014, or BWP switching 1016 in FIG. 10) may be based on a command from the base station. The command may be a DCI comprising scheduling information for the UE in the second BWP. In case of uplink BWP switching, the first BWP and the second BWP may be uplink BWPs and the scheduling information may be an uplink grant for uplink transmission via the second BWP. In case of downlink BWP switching, the first BWP and the second BWP may be downlink BWPs and the scheduling information may be a downlink assignment for downlink reception via the second BWP.

The BWP switching (e.g., BWP switching 1010, BWP switching 1012, BWP switching 1014, or BWP switching 1016 in FIG. 10) may be based on an expiry of a timer. The base station may configure a wireless device with a BWP inactivity timer and the wireless device may switch to a default BWP (e.g., default downlink BWP) based on the expiry of the BWP inactivity timer. The expiry of the BWP inactivity timer may be an indication of low activity on the current active downlink BWP. The base station may configure the wireless device with the default downlink BWP. If the base station does not configure the wireless device with the default BWP, the default BWP may be an initial downlink BWP. The initial active BWP may be the BWP that the wireless device receives scheduling information for remaining system information upon transition to an RRC_CONNECTED state.

A wireless device may monitor a downlink control channel of a downlink BWP. For example, the UE may monitor a set of PDCCH candidates in configured monitoring occasions in one or more configured COntrol REsource SETs (CORESETs) according to the corresponding search space configurations. A search space configuration may define how/where to search for PDCCH candidates. For example, the search space configuration parameters may comprise a monitoring periodicity and offset parameter indicating the slots for monitoring the PDCCH candidates. The search space configuration parameters may further comprise a parameter indicating a first symbol with a slot within the slots determined for monitoring PDCCH candidates. A search space may be associated with one or more CORESETs and the search space configuration may indicate one or more identifiers of the one or more CORESETs. The search space configuration parameters may further indicate that whether the search space is a common search space or a UE-specific search space. A common search space may be monitored by a plurality of wireless devices and a UE-specific search space may be dedicated to a specific UE.

FIG. 11A shows example arrangements of carriers in carrier aggregation in accordance with several of various embodiments of the present disclosure. With carrier aggregation, multiple NR component carriers (CCs) may be aggregated. Downlink transmissions to a wireless device may take place simultaneously on the aggregated downlink CCs resulting in higher downlink data rates. Uplink transmissions from a wireless device may take place simultaneously on the aggregated uplink CCs resulting in higher uplink data rates. The component carriers in carrier aggregation may be on the same frequency band (e.g., intra-band carrier aggregation) or on different frequency bands (e.g., inter-band carrier aggregation). The component carriers may also be contiguous or non-contiguous. This results in three possible carrier aggregation scenarios, intra-band contiguous CA 1102, intra-band non-contiguous CA 1104 and inter-band CA 1106 as shown in FIG. 11A. Depending on the UE capability for carrier aggregation, a UE may transmit and/or receive on multiple carriers or for a UE that is not capable of carrier aggregation, the UE may transmit and/or receive on one component carrier at a time. In this disclosure, the carrier aggregation is described using the term cell and a carrier aggregation capable UE may transmit and/or receive via multiple cells.

In carrier aggregation, a UE may be configured with multiple cells. A cell of the multiple cells configured for the UE may be referred to as a Primary Cell (PCell). The PCell may be the first cell that the UE is initially connected to. One or more other cells configured for the UE may be referred to as Secondary Cells (SCells). The base station may configure a UE with multiple SCells. The configured SCells may be deactivated upon configuration and the base station may dynamically activate or deactivate one or more of the configured SCells based on traffic and/or channel conditions. The base station may activate or deactivate configured SCells using a SCell Activation/Deactivation MAC CE. The SCell Activation/Deactivation MAC CE may comprise a bitmap, wherein each bit in the bitmap may correspond to a SCell and the value of the bit indicates an activation status or deactivation status of the SCell.

An SCell may also be deactivated in response to expiry of a SCell deactivation timer of the SCell. The expiry of an SCell deactivation timer of an SCell may be an indication of low activity (e.g., low transmission or reception activity) on the SCell. The base station may configure the SCell with an SCell deactivation timer. The base station may not configure an SCell deactivation timer for an SCell that is configured with PUCCH (also referred to as a PUCCH SCell). The configuration of the SCell deactivation timer may be per configured SCell and different SCells may be configured with different SCell deactivation timer values. The SCell deactivation timer may be restarted based on one or more criteria including reception of downlink control information on the SCell indicating uplink grant or downlink assignment for the SCell or reception of downlink control information on a scheduling cell indicating uplink grant or downlink assignment for the SCell or transmission of a MAC PDU based on a configured uplink grant or reception of a configured downlink assignment.

A PCell for a UE may be an SCell for another UE and a SCell for a UE may be PCell for another UE. The configuration of PCell may be UE-specific. One or more SCells of the multiple SCells configured for a UE may be configured as downlink-only SCells, e.g., may only be used for downlink reception and may not be used for uplink transmission. In case of self-scheduling, the base station may transmit signaling for uplink grants and/or downlink assignments on the same cell that the corresponding uplink or downlink transmission takes place. In case of cross-carrier scheduling, the base station may transmit signaling for uplink grants and/or downlink assignments on a cell different from the cell that the corresponding uplink or downlink transmission takes place.

FIG. 11B shows examples of uplink control channel groups in accordance with several of various embodiments of the present disclosure. A base station may configure a UE with multiple PUCCH groups wherein a PUCCH group comprises one or more cells. For example, as shown in FIG. 11B, the base station may configure a UE with a primary PUCCH group 1114 and a secondary PUCCH group 1116. The primary PUCCH group may comprise the PCell 1110 and one or more first SCells. First UCI corresponding to the PCell and the one or more first SCells of the primary PUCCH group may be transmitted by the PUCCH of the PCell. The first UCI may be, for example, HARQ feedback for downlink transmissions via downlink CCs of the PCell and the one or more first SCells. The secondary PUCCH group may comprise a PUCCH SCell and one or more second SCells. Second UCI corresponding to the PUCCH SCell and the one or more second SCells of the secondary PUCCH group may be transmitted by the PUCCH of the PUCCH SCell. The second UCI may be, for example, HARQ feedback for downlink transmissions via downlink CCs of the PUCCH SCell and the one or more second SCells.

FIG. 12A, FIG. 12B and FIG. 12C show example random access processes in accordance with several of various embodiments of the present disclosure. FIG. 12A shows an example of four step contention-based random access (CBRA) procedure. The four-step CBRA procedure includes exchanging four messages between a UE and a base station. Msg1 may be for transmission (or retransmission) of a random access preamble by the wireless device to the base station. Msg2 may be the random access response (RAR) by the base station to the wireless device. Msg3 is the scheduled transmission based on an uplink grant indicated in Msg2 and Msg4 may be for contention resolution.

The base station may transmit one or more RRC messages comprising configuration parameters of the random access parameters. The random access parameters may indicate radio resources (e.g., time-frequency resources) for transmission of the random access preamble (e.g., Msg1), configuration index, one or more parameters for determining the power of the random access preamble (e.g., a power ramping parameter, a preamble received target power, etc.), a parameter indicating maximum number of preamble transmission, RAR window for monitoring RAR, cell-specific random access parameters and UE specific random access parameters. The UE-specific random access parameters may indicate one or more PRACH occasions for random access preamble (e.g., Msg1) transmissions. The random access parameters may indicate association between the PRACH occasions and one or more reference signals (e.g., SSB or CSI-RS). The random access parameters may further indicate association between the random access preambles and one or more reference signals (e.g., SBB or CSI-RS). The UE may use one or more reference signals (e.g., SSB(s) or CSI-RS(s)) and may determine a random access preamble to use for Msg1 transmission based on the association between the random access preambles and the one or more reference signals. The UE may use one or more reference signals (e.g., SSB(s) or CSI-RS(s)) and may determine the PRACH occasion to use for Msg1 transmission based on the association between the PRACH occasions and the reference signals. The UE may perform a retransmission of the random access preamble if no response is received with the RAR window following the transmission of the preamble. UE may use a higher transmission power for retransmission of the preamble. UE may determine the higher transmission power of the preamble based on the power ramping parameter.

Msg2 is for transmission of RAR by the base station. Msg2 may comprise a plurality of RARs corresponding to a plurality of random access preambles transmitted by a plurality of UEs. Msg2 may be associated with a random access temporary radio identifier (RA-RNTI) and may be received in a common search space of the UE. The RA-RNTI may be based on the PRACH occasion (e.g., time and frequency resources of a PRACH) in which a random access preamble is transmitted. RAR may comprise a timing advance command for uplink timing adjustment at the UE, an uplink grant for transmission of Msg3 and a temporary C-RNTI. In response to the successful reception of Msg2, the UE may transmit the Msg3. Msg3 and Msg4 may enable contention resolution in case of CBRA. In a CBRA, a plurality of UEs may transmit the same random access preamble and may consider the same RAR as being corresponding to them. UE may include a device identifier in Msg3 (e.g., a C-RNTI, temporary C-RNTI or other UE identity). Base station may transmit the Msg4 with a PDSCH and UE may assume that the contention resolution is successful in response to the PDSCH used for transmission of Msg4 being associated with the UE identifier included in Msg3.

FIG. 12B shows an example of a contention-free random access (CFRA) process. Msg 1 (random access preamble) and Msg 2 (random access response) in FIG. 12B for CFRA may be analogous to Msg 1 and Msg 2 in FIG. 12A for CBRA. In an example, the CFRA procedure may be initiated in response to a PDCCH order from a base station. The PDCCH order for initiating the CFRA procedure by the wireless device may be based on a DCI having a first format (e.g., format 1_0). The DCI for the PDCCH order may comprise a random access preamble index, an UL/SUL indicator indicating an uplink carrier of a cell (e.g., normal uplink carrier or supplementary uplink carrier) for transmission of the random access preamble, a SS/PBCH index indicating the SS/PBCH that may be used to determine a RACH occasion for PRACH transmission, a PRACH mask index indicating the RACH occasion associated with the SS/PBCH indicated by the SS/PBCH index for PRACH transmission, etc. In an example, the CFRA process may be started in response to a beam failure recovery process. The wireless device may start the CFRA for the beam failure recovery without a command (e.g., PDCCH order) from the base station and by using the wireless device dedicated resources.

FIG. 12C shows an example of a two-step random access process comprising two messages exchanged between a wireless device and a base station. Msg A may be transmitted by the wireless device to the base station and may comprise one or more transmissions of a preamble and/or one or more transmissions of a transport block. The transport block in Msg A and Msg 3 in FIG. 12A may have similar and/or equivalent contents. The transport block of Msg A may comprise data and control information (e.g., SR, HARQ feedback, etc.). In response to the transmission of Msg A, the wireless device may receive Msg B from the base station. Msg B in FIG. 12C and Msg 2 (e.g., RAR) illustrated in FIGS. 12A and 12B may have similar and/or equivalent content.

The base station may periodically transmit synchronization signals (SSs), e.g., primary SS (PSS) and secondary SS (SSS) along with PBCH on each NR cell. The PSS/SSS together with PBCH is jointly referred to as a SS/PBCH block. The SS/PBCH block enables a wireless device to find a cell when entering to the mobile communications network or find new cells when moving within the network. The SS/PBCH block spans four OFDM symbols in time domain. The PSS is transmitted in the first symbol and occupies 127 subcarriers in frequency domain. The SSS is transmitted in the third OFDM symbol and occupies the same 127 subcarriers as the PSS. There are eight and nine empty subcarriers on each side of the SSS. The PBCH is transmitted on the second OFDM symbol occupying 240 subcarriers, the third OFDM symbol occupying 48 subcarriers on each side of the SSS, and on the fourth OFDM symbol occupying 240 subcarriers. Some of the PBCH resources indicated above may be used for transmission of the demodulation reference signal (DMRS) for coherent demodulation of the PBCH. The SS/PBCH block is transmitted periodically with a period ranging from 5 ms to 160 ms. For initial cell search or for cell search during inactive/idle state, a wireless device may assume that that the SS/PBCH block is repeated at least every 20 ms.

In NR, transmissions using of antenna arrays, with many antenna elements, and beamforming plays an important role specially in higher frequency bands. Beamforming enables higher capacity by increasing the signal strength (e.g., by focusing the signal energy in a specific direction) and by lowering the amount interference received at the wireless devices. The beamforming techniques may generally be divided to analog beamforming and digital beamforming techniques. With digital beamforming, signal processing for beamforming is carried out in the digital domain before digital-to-analog conversion and detailed control of both amplitude and phase of different antenna elements may be possible. With analog beamforming, the signal processing for beamforming is carried out in the analog domain and after the digital to analog conversion. The beamformed transmissions may be in one direction at a time. For example, the wireless devices that are in different directions relative to the base station may receive their downlink transmissions at different times. For analog receiver-side beamforming, the receiver may focus its receiver beam in one direction at a time.

In NR, the base station may use beam sweeping for transmission of SS/PBCH blocks. The SS/PBCH blocks may be transmitted in different beams using time multiplexing. The set of SS/PBCH blocks that are transmitted in one beam sweep may be referred to as a SS/PBCH block set. The period of PBCH/SSB block transmission may be a time duration between a SS/PBCH block transmission in a beam and the next SS/PBCH block transmission in the same beam. The period of SS/PBCH block is, therefore, also the period of the SS/PBCH block set.

FIG. 13A shows example time and frequency structure of SS/PBCH blocks and their associations with beams in accordance with several of various embodiments of the present disclosure. In this example, a SS/PBCH block (also referred to as SSB) set comprise L SSBs wherein an SSB in the SSB set is associated with (e.g., transmitted in) one of L beams of a cell. The transmission of SBBs of an SSB set may be confined within a 5 ms interval, either in a first half-frame or a second half-frame of a 10 ms frame. The number of SSBs in an SSB set may depend on the frequency band of operation. For example, the number of SSBs in a SSB set may be up to four SSBs in frequency bands below 3 GHz enabling beam sweeping of up to four beams, up to eight SSBs in frequency bands between 3 GHz and 6 GHz enabling beam sweeping of up to eight beams, and up to sixty four SSBs in higher frequency bands enabling beam sweeping of up to sixty four beams. The SSs of an SSB may depend on a physical cell identity (PCI) of the cell and may be independent of which beam of the cell is used for transmission of the SSB. The PBCH of an SSB may indicate a time index parameter and the wireless device may determine the relative position of the SSB within the SSB set using the time index parameter. The wireless device may use the relative position of the SSB within an SSB set for determining the frame timing and/or determining RACH occasions for a random access process.

A wireless device entering the mobile communications network may first search for the PSS. After detecting the PSS, the wireless device may determine the synchronization up to the periodicity of the PSS. By detecting the PSS, the wireless device may determine the transmission timing of the SSS. The wireless device may determine the PCI of the cell after detecting the SSS. The PBCH of a SS/PBCH block is a downlink physical channel that carries the MIB. The MIB may be used by the wireless device to obtain remaining system information (RMSI) that is broadcast by the network. The RMSI may include System Information Block 1 (SIB1) that contains information required for the wireless device to access the cell.

As discussed earlier, the wireless device may determine a time index parameter from the SSB. The PBCH comprises a half-frame parameter indicating whether the SSB is in the first 5 ms half or the second 5 ms half of a 10 ms frame. The wireless device may determine the frame boundary using the time index parameter and the half-frame parameter. In addition, the PBCH may comprise a parameter indicating the system frame number (SFN) of the cell.

The base station may transmit CSI-RS and a UE may measure the CSI-RS to obtain channel state information (CSI). The base station may configure the CSI-RS in a UE-specific manner. In some scenarios, same set of CSI-RS resources may be configured for multiple UEs and one or more resource elements of a CSI-RS resource may be shared among multiple UEs. A CSI-RS resource may be configured such that it does not collide with a CORESET configured for the wireless device and/or with a DMRS of a PDSCH scheduled for the wireless device and/or transmitted SSBs. The UE may measure one or more CSI-RSs configured for the UE and may generate a CSI report based on the CSI-RS measurements and may transmit the CSI report to the base station for scheduling, link adaptation and/or other purposes.

NR supports flexible CSI-RS configurations. A CSI-RS resource may be configured with single or multiple antenna ports and with configurable density. Based on the number of configured antenna ports, a CSI-RS resource may span different number of OFDM symbols (e.g., 1, 2, and 4 symbols). The CSI-RS may be configured for a downlink BWP and may use the numerology of the downlink BWP. The CSI-RS may be configured to cover the full bandwidth of the downlink BWP or a portion of the downlink BWP. In some case, the CSI-RS may be repeated in every resource block of the CSI-RS bandwidth, referred to as CSI-RS with density equal to one. In some cases, the CSI-RS may be configured to be repeated in every other resource block of the CSI-RS bandwidth. CSI-RS may be non-zero power (NZP) CSI-RS or zero-power (ZP) CSI-RS.

The base station may configure a wireless device with one or more sets of NZP CSI-RS resources. The base station may configure the wireless device with a NZP CSI-RS resource set using an RRC information element (IE) NZP-CSI-RS-ResourceSet indicating a NZP CSI-RS resource set identifier (ID) and parameters specific to the NZP CSI-RS resource set. An NZP CSI-RS resource set may comprise one or more CSI-RS resources. An NZP CSI-RS resource set may be configured as part of the CSI measurement configuration.

The CSI-RS may be configured for periodic, semi-persistent or aperiodic transmission. In case of the periodic and semi-persistent CSI-RS configurations, the wireless device may be configured with a CSI resource periodicity and offset parameter that indicate a periodicity and corresponding offset in terms of number of slots. The wireless device may determine the slots that the CSI-RSs are transmitted. For semi-persistent CSI-RS, the CSI-RS resources for CSI-RS transmissions may be activated and deactivated by using a semi-persistent (SP) CSI-CSI Resource Set Activation/Deactivation MAC CE. In response to receiving a MAC CE indicating activation of semi-persistent CSI-RS resources, the wireless device may assume that the CSI-RS transmissions will continue until the CSI-RS resources for CSI-RS transmissions are activated.

As discussed before, CSI-RS may be configured for a wireless device as NZP CSI-RS or ZP CSI-RS. The configuration of the ZP CSI-RS may be similar to the NZP CSI-RS with the difference that the wireless device may not carry out measurements for the ZP CSI-RS. By configuring ZP CSI-RS, the wireless device may assume that a scheduled PDSCH that includes resource elements from the ZP CSI-RS is rate matched around those ZP CSI-RS resources. For example, a ZP CSI-RS resource configured for a wireless device may be an NZP CSI-RS resource for another wireless device. For example, by configuring ZP CSI-RS resources for the wireless device, the base station may indicate to the wireless device that the PDSCH scheduled for the wireless device is rate matched around the ZP CSI-RS resources.

A base station may configure a wireless device with channel state information interference measurement (CSI-IM) resources. Similar to the CSI-RS configuration, configuration of locations and density of CSI-IM resources may be flexible. The CSI-IM resources may be periodic (configured with a periodicity), semi-persistent (configured with a periodicity and activated and deactivated by MAC CE) or aperiodic (triggered by a DCI).

Tracking reference signals (TRSs) may be configured for a wireless device as a set of sparse reference signals to assist the wireless in time and frequency tracking and compensating time and frequency variations in its local oscillator. The wireless device may further use the TRSs for estimating channel characteristics such as delay spread or doppler frequency. The base station may use a CSI-RS configuration for configuring TRS for the wireless device. The TRS may be configured as a resource set comprising multiple periodic NZP CSI-RS resources.

A base station may configure a UE and the UE may transmit sounding reference signals (SRSs) to enable uplink channel sounding/estimation at the base station. The SRS may support up to four antenna ports and may be designed with low cubic metric enabling efficient operation of the wireless device amplifier. The SRS may span one or more (e.g., one, two or four) consecutive OFDM symbols in time domain and may be located within the last n (e.g., six) symbols of a slot. In the frequency domain, the SRS may have a structure that is referred to as a comb structure and may be transmitted on every Nth subcarrier. Different SRS transmissions from different wireless devices may have different comb structures and may be multiplexed in frequency domain.

A base station may configure a wireless device with one or more SRS resource sets and an SRS resource set may comprise one or more SRS resources. The SRS resources in an SRS resources set may be configured for periodic, semi-persistent or aperiodic transmission. The periodic SRS and the semi-persistent SRS resources may be configured with periodicity and offset parameters. The Semi-persistent SRS resources of a configured semi-persistent SRS resource set may be activated or deactivated by a semi-persistent (SP) SRS Activation/Deactivation MAC CE. The set of SRS resources included in an aperiodic SRS resource set may be activated by a DCI. A value of a field (e.g., an SRS request field) in the DCI may indicate activation of resources in an aperiodic SRS resource set from a plurality of SRS resource sets configured for the wireless device.

An antenna port may be associated with one or more reference signals. The receiver may assume that the one or more reference signals, associated with the antenna port, may be used for estimating channel corresponding to the antenna port. The reference signals may be used to derive channel state information related to the antenna port. Two antenna ports may be referred to as quasi co-located if characteristics (e.g., large-scale properties) of the channel over which a symbol is conveyed on one antenna port may be inferred from the channel over which a symbol is conveyed from another antenna port. For example, a UE may assume that radio channels corresponding to two different antenna ports have the same large-scale properties if the antenna ports are specified as quasi co-located. In some cases, the UE may assume that two antenna ports are quasi co-located based on signaling received from the base station. Spatial quasi-colocation (QCL) between two signals may be, for example, due to the two signals being transmitted from the same location and in the same beam. If a receive beam is good for a signal in a group of signals that are spatially quasi co-located, it may be assumed also be good for the other signals in the group of signals.

The CSI-RS in the downlink and the SRS in uplink may serve as quasi-location (QCL) reference for other physical downlink channels and physical uplink channels, respectively. For example, a downlink physical channel (e.g., PDSCH or PDCCH) may be spatially quasi co-located with a downlink reference signal (e.g., CSI-RS or SSB). The wireless device may determine a receive beam based on measurement on the downlink reference signal and may assume that the determined received beam is also good for reception of the physical channels (e.g., PDSCH or PDCCH) that are spatially quasi co-located with the downlink reference signal. Similarly, an uplink physical channel (e.g., PUSCH or PUCCH) may be spatially quasi co-located with an uplink reference signal (e.g., SRS). The base station may determine a receive beam based on measurement on the uplink reference signal and may assume that the determined received beam is also good for reception of the physical channels (e.g., PUSCH or PUCCH) that are spatially quasi co-located with the uplink reference signal.

The Demodulation Reference Signals (DM-RSs) enables channel estimation for coherent demodulation of downlink physical channels (e.g., PDSCH, PDCCH and PBH) and uplink physical channels (e.g., PUSCH and PUCCH). The DM-RS may be located early in the transmission (e.g., front-loaded DM-RS) and may enable the receiver to obtain the channel estimate early and reduce the latency. The time-domain structure of the DM-RS (e.g., symbols wherein the DM-RS are located in a slot) may be based on different mapping types.

The Phase Tracking Reference Signals (PT-RSs) enables tracking and compensation of phase variations across the transmission duration. The phase variations may be, for example, due to oscillator phase noise. The oscillator phase noise may become more sever in higher frequencies (e.g., mmWave frequency bands). The base station may configure the PT-RS for uplink and/or downlink. The PT-RS configuration parameters may indicate frequency and time density of PT-RS, maximum number of ports (e.g., uplink ports), resource element offset, configuration of uplink PT-RS without transform precoder (e.g., CP-OFDM) or with transform precoder (e.g., DFT-s-OFDM), etc. The subcarrier number and/or resource blocks used for PT-RS transmission may be based on the C-RNTI of the wireless device to reduce risk of collisions between PT-RSs of wireless devices scheduled on overlapping frequency domain resources.

FIG. 13B shows example time and frequency structure of CSI-RSs and their association with beams in accordance with several of various embodiments of the present disclosure. A beam of the L beams shown in FIG. 13B may be associated with a corresponding CSI-RS resource. The base station may transmit the CSI-RSs using the configured CSI-RS resources and a UE may measure the CSI-RSs (e.g., received signal received power (RSRP) of the CSI-RSs) and report the CSI-RS measurements to the base station based on a reporting configuration. For example, the base station may determine one or more transmission configuration indication (TCI) states and may indicate the one or more TCI states to the UE (e.g., using RRC signaling, a MAC CE and/or a DCI). Based on the one or more TCI states indicated to the UE, the UE may determine a downlink receive beam and receive downlink transmissions using the receive beam. In case of a beam correspondence, the UE may determine a spatial domain filter of a transmit beam based on spatial domain filter of a corresponding receive beam. Otherwise, the UE may perform an uplink beam selection procedure to determine the spatial domain filter of the transmit beam. The UE may transmit one or more SRSs using the SRS resources configured for the UE and the base station may measure the SRSs and determine/select the transmit beam for the UE based the SRS measurements. The base station may indicate the selected beam to the UE. The CSI-RS resources shown in FIG. 13B may be for one UE. The base station may configure different CSI-RS resources associated with a given beam for different UEs by using frequency division multiplexing.

A base station and a wireless device may perform beam management procedures to establish beam pairs (e.g., transmit and receive beams) that jointly provide good connectivity. For example, in the downlink direction, the UE may perform measurements for a beam pair and estimate channel quality for a transmit beam by the base station (or a transmission reception point (TRP) more generally) and the receive beam by the UE. The UE may transmit a report indicating beam pair quality parameters. The report may comprise one or more parameters indicating one or more beams (e.g., a beam index, an identifier of reference signal associated with a beam, etc.), one or more measurement parameters (e.g., RSRP), a precoding matrix indicator (PMI), a channel quality indicator (CQI), and/or a rank indicator (RI).

FIG. 14A, FIG. 14B and FIG. 14C show example beam management processes (referred to as P1, P2 and P3, respectively) in accordance with several of various embodiments of the present disclosure. The P1 process shown in FIG. 14A may enable, based on UE measurements, selection of a base station (or TRP more generally) transmit beam and/or a wireless device receive beam. The TRP may perform a beam sweeping procedure where the TRP may sequentially transmit reference signals (e.g., SSB and/or CSI-RS) on a set of beams and the UE may select a beam from the set of beams and may report the selected beam to the TRP. The P2 procedure as shown in FIG. 14B may be a beam refinement procedure. The selection of the TRP transmit beam and the UE receive beam may be regularly reevaluated due to movements and/or rotations of the UE or movement of other objects. In an example, the base station may perform the beam sweeping procedure over a smaller set of beams and the UE may select the best beam over the smaller set. In an example, the beam shape may be narrower compared to beam selected based on the P1 procedure. Using the P3 procedure as shown in FIG. 14C, the TRP may fix its transmit beam and the UE may refine its receive beam.

A wireless device may receive one or more messages from a base station. The one or more messages may comprise one or more RRC messages. The one or more messages may comprise configuration parameters of a plurality of cells for the wireless device. The plurality of cells may comprise a primary cell and one or more secondary cells. For example, the plurality of cells may be provided by a base station and the wireless device may communicate with the base station using the plurality of cells. For example, the plurality of cells may be provided by multiple base station (e.g., in case of dual and/or multi-connectivity). The wireless device may communicate with a first base station, of the multiple base stations, using one or more first cells of the plurality of cells. The wireless device may communicate with a second base station of the multiple base stations using one or more second cells of the plurality of cells.

The one or more messages may comprise configuration parameters used for processes in physical, MAC, RLC, PCDP, SDAP, and/or RRC layers of the wireless device. For example, the configuration parameters may include values of timers used in physical, MAC, RLC, PCDP, SDAP, and/or RRC layers. For example, the configuration parameters may include parameters for configurating different channels (e.g., physical layer channel, logical channels, RLC channels, etc.) and/or signals (e.g., CSI-RS, SRS, etc.).

Upon starting a timer, the timer may start running until the timer is stopped or until the timer expires. A timer may be restarted if it is running. A timer may be started if it is not running (e.g., after the timer is stopped or after the timer expires). A timer may be configured with or may be associated with a value (e.g., an initial value). The timer may be started or restarted with the value of the timer. The value of the timer may indicate a time duration that the timer may be running upon being started or restarted and until the timer expires. The duration of a timer may not be updated until the timer is stopped or expires (e.g., due to BWP switching). This specification may disclose a process that includes one or more timers. The one or more timers may be implemented in multiple ways. For example, a timer may be used by the wireless device and/or base station to determine a time window [t1, t2], wherein the timer is started at time t1 and expires at time t2 and the wireless device and/or the base station may be interested in and/or monitor the time window [t1, t2], for example to receive a specific signaling. Other examples of implementation of a timer may be provided.

FIG. 15 shows example components of a wireless device and a base station that are in communication via an air interface in accordance with several of various embodiments of the present disclosure. The wireless device 1502 may communicate with the base station 1542 over the air interface 1532. The wireless device 1502 may include a plurality of antennas. The base station 1542 may include a plurality of antennas. The plurality of antennas at the wireless device 1502 and/or the base station 1542 enables different types of multiple antenna techniques such as beamforming, single-user and/or multi-user MIMO, etc.

The wireless device 1502 and the base station 1542 may have one or more of a plurality of modules/blocks, for example RF front end (e.g., RF front end 1530 at the wireless device 1502 and RF front end 1570 at the base station 1542), Data Processing System (e.g., Data Processing System1524 at the wireless device 1502 and Data Processing System1564 at the base station 1542), Memory (e.g., Memory 1512 at the wireless device 1502 and Memory 1542 at the base station1542). Additionally, the wireless device 1502 and the base station 1542 may have other modules/blocks such as GPS (e.g., GPS 1514 at the wireless device 1502 and GPS 1554 at the base station 1542).

An RF front end module/block may include circuitry between antennas and a Data Processing System for proper conversion of signals between these two modules/blocks. An RF front end may include one or more filters (e.g., Filter(s) 1526 at RF front end 1530 or Filter(s) 1566 at the RF front end 1570), one or more amplifiers (e.g., Amplifier(s) 1528 at the RF front end 1530 and Amplifier(s) 1568 at the RF front end 1570). The Amplifier(s) may comprise power amplifier(s) for transmission and low-noise amplifier(s) (LNA(s)) for reception.

The Data Processing System 1524 and the Data Processing System 1564 may process the data to be transmitted or the received signals by implementing functions at different layers of the protocol stack such as PHY, MAC, RLC, etc. Example PHY layer functions that may be implemented by the Data Processing System1524 and/or 1564 may include forward error correction, interleaving, rate matching, modulation, precoding, resource mapping, MIMO processing, etc. Similarly, one or more functions of the MAC layer, RLC layer and/or other layers may be implemented by the Data Processing System1524 and/or the Data Processing System1564. One or more processes described in the present disclosure may be implemented by the Data Processing System1524 and/or the Data Processing System1564. A Data Processing System may include an RF module (RF module 1516 at the Data Processing System1524 and RF module 1556 at the Data Processing System1564) and/or a TX/RX processor (e.g., TX/RX processor 1518 at the Data Processing System1524 and TX/RX processor 1558 at the Data Processing System1566) and/or a central processing unit (CPU) (e.g., CPU 1520 at the Data Processing System1524 and CPU 1560 at the Data Processing System1564) and/or a graphical processing unit (GPU) (e.g., GPU 1522 at the Data Processing System1524 and GPU 1562 at the Data Processing System1564).

The Memory 1512 may have interfaces with the Data Processing System 1524 and the Memory 1552 may have interfaces with Data Processing System1564, respectively. The Memory 1512 or the Memory 1552 may include non-transitory computer readable mediums (e.g., Storage Medium 1510 at the Memory 1512 and Storage Medium 1550 at the Memory 1552) that may store software code or instructions that may be executed by the Data Processing System1524 and Data Processing System1564, respectively, to implement the processes described in the present disclosure. The Memory 1512 or the Memory 1552 may include random-access memory (RAM) (e.g., RAM 1506 at the Memory 1512 or RAM 1546 at the Memory 1552) or read-only memory (ROM) (e.g., ROM 1508 at the Memory 1512 or ROM 1548 at the Memory 1552) to store data and/or software codes.

The Data Processing System1524 and/or the Data Processing System1564 may be connected to other components such as a GPS module 1514 and a GPS module 1554, respectively, wherein the GPS module 1514 and a GPS module 1554 may enable delivery of location information of the wireless device 1502 to the Data Processing System1524 and location information of the base station 1542 to the Data Processing System1564. One or more other peripheral components (e.g., Peripheral Component(s) 1504 or Peripheral Component(s) 1544) may be configured and connected to the data Processing System1524 and data Processing System1564, respectively.

In example embodiments, a wireless device may be configured with parameters and/or configuration arrangements. For example, the configuration of the wireless device with parameters and/or configuration arrangements may be based on one or more control messages that may be used to configure the wireless device to implement processes and/or actions. The wireless device may be configured with the parameters and/or the configuration arrangements regardless of the wireless device being in operation or not in operation. For example, software, firmware, memory, hardware and/or a combination thereof and/or alike may be configured in a wireless device regardless of the wireless device being in operation or not operation. The configured parameters and/or settings may influence the actions and/or processes performed by the wireless device when in operation.

In example embodiments, a wireless device may receive one or more message comprising configuration parameters. For example, the one or more messages may comprise radio resource control (RRC) messages. A parameter of the configuration parameters may be in at least one of the one or more messages. The one or more messages may comprise information element (IEs). An information element may be a structural element that includes single or multiple fields. The fields in an IE may be individual contents of the IE. The terms configuration parameter, IE and field may be used equally in this disclosure. The IEs may be implemented using a nested structure, wherein an IE may include one or more other IEs and an IE of the one or more other IEs may include one or more additional IEs. With this structure, a parent IE contains all the offspring IEs as well. For example, a first IE containing a second IE, the second IE containing a third IE, and the third IE containing a fourth IE may imply that the first IE contains the third IE and the fourth IE.

In an example, an Xn User plane (Xn-U) interface may be defined between two NG-RAN nodes. An example user plane protocol stack on the Xn interface is shown in FIG. 16A. The transport network layer may be built on IP transport and GTP-U may be used on top of UDP/IP to carry the user plane PDUs. The Xn-U interface may provide non-guaranteed delivery of user plane PDUs and may support data forwarding and flow control.

In an example, the Xn control plane interface (Xn-C) may be defined between two NG-RAN nodes. An example control plane protocol stack of the Xn interface is shown in FIG. 16B. The transport network layer may be built on SCTP on top of IP. The application layer signalling protocol may be referred to as XnAP (Xn Application Protocol). The SCTP layer may provide the guaranteed delivery of application layer messages. In the transport IP layer point-to-point transmission may be used to deliver the signaling PDUs. The Xn-C interface may support Xn interface management; UE mobility management, including context transfer and RAN paging; and dual connectivity.

In an example, Network controlled mobility may apply to UEs in RRC_CONNECTED and may be categorized into two types of mobility: cell level mobility and beam level mobility.

In an example, cell level mobility may require explicit RRC signaling to be triggered, e.g., handover. For inter-gNB handover, the signaling procedures may comprise at least the following elemental components as shown in FIG. 17. The source gNB may initiate handover and may issue a HANDOVER REQUEST over the Xn interface. The target gNB may perform admission control and may provide the new RRC configuration as part of the HANDOVER REQUEST ACKNOWLEDGE. The source gNB may provide the RRC configuration to the wireless device by forwarding the RRCReconfiguration message received in the HANDOVER REQUEST ACKNOWLEDGE. The RRCReconfiguration message may include at least cell ID and information required to access the target cell so that the wireless device may access the target cell without reading system information. For some cases, the information required for contention-based and contention-free random access may be included in the RRCReconfiguration message. The access information to the target cell may include beam specific information, if any.

The wireless device may move the RRC connection to the target gNB and may reply with the RRCReconfigurationComplete.

In an example, a handover mechanism triggered by RRC may require the wireless device at least to reset the MAC entity and re-establish RLC. RRC managed handovers with and without PDCP entity re-establishment may be both supported. For DRBs using RLC AM mode, PDCP may either be re-established together with a security key change or may initiate a data recovery procedure without a key change. For DRBs using RLC UM mode and for SRBs, PDCP may either be re-established together with a security key change or may remain as it is without a key change.

In an example, data forwarding, in-sequence delivery and duplication avoidance at handover may be guaranteed when the target gNB uses the same DRB configuration as the source gNB.

In an example, timer-based handover failure procedure may be supported in NR. RRC connection re-establishment procedure may be used for recovering from handover failure.

In an example, beam level mobility may not require explicit RRC signaling to be triggered. The gNB may provide, via RRC signaling, the wireless device with measurement configuration containing configurations of SSB/CSI resources and resource sets, reports and trigger states for triggering channel and interference measurements and reports. Beam level mobility may then be dealt with at lower layers by means of physical layer and MAC layer control signaling, and RRC may not be required to know which beam is being used at a given point in time.

In an example, SSB-based beam level mobility may be based on the SSB associated to the initial DL BWP and may be configured for the initial DL BWPs and for DL BWPs containing the SSB associated to the initial DL BWP. For other DL BWPs, beam level mobility may be performed based on CSI-RS.

In an example, the intra-NR RAN handover may perform the preparation and execution phase of the handover procedure performed without involvement of the 5GC, e.g., preparation messages may be directly exchanged between the gNBs. The release of the resources at the source gNB during the handover completion phase may be triggered by the target gNB. FIG. 18 shows an example basic handover scenario where neither the AMF nor the UPF changes:

-   0. The UE context within the source gNB may contain information     regarding roaming and access restrictions which may be provided     either at connection establishment or at the last TA update. -   1. The source gNB may configure the UE measurement procedures and     the UE may report according to the measurement configuration. -   2. The source gNB may decide to handover the UE, based on     MeasurementReport and RRM information. -   3. The source gNB may issue a Handover Request message to the target     gNB passing a transparent RRC container with necessary information     to prepare the handover at the target side. The information may     include at least the target cell ID, the C-RNTI of the UE in the     source gNB, RRM-configuration including UE inactive time, basic     AS-configuration including antenna Info and DL Carrier Frequency,     the current QoS flow to DRB mapping rules applied to the UE, the     SIB1 from source gNB, the UE capabilities for different RATs, PDU     session related information, and may include the UE reported     measurement information including beam-related information if     available. The PDU session related information may include the slice     information and QoS flow level QoS profile(s). -   4. Admission Control may be performed by the target gNB. Slice-aware     admission control may be performed if the slice information is sent     to the target gNB. If the PDU sessions are associated with     non-supported slices the target gNB may reject such PDU sessions. -   5. The target gNB may prepare the handover with L1/L2 and sends the     HANDOVER REQUEST ACKNOWLEDGE to the source gNB, which may include a     transparent container to be sent to the UE as an RRC message to     perform the handover. -   6. The source gNB may trigger the Uu handover by sending an     RRCReconfiguration message to the UE, containing the information     required to access the target cell: at least the target cell ID, the     new C-RNTI, the target gNB security algorithm identifiers for the     selected security algorithms. It may also include a set of dedicated     RACH resources, the association between RACH resources and SSB(s),     the association between RACH resources and UE-specific CSI-RS     configuration(s), common RACH resources, and system information of     the target cell, etc. -   7. The source gNB may send the SN STATUS TRANSFER message to the     target gNB. -   8. The UE may synchronize to the target cell and may complete the     RRC handover procedure by sending RRCReconfigurationComplete message     to target gNB. -   9. The target gNB may send a PATH SWITCH REQUEST message to AMF to     trigger 5GC to switch the DL data path towards the target gNB and to     establish an NG-C interface instance towards the target gNB. -   10. 5GC may switch the DL data path towards the target gNB. The UPF     may send one or more “end marker” packets on the old path to the     source gNB per PDU session/tunnel and then may release any     U-plane/TNL resources towards the source gNB. -   11. The AMF may confirm the PATH SWITCH REQUEST message with the     PATH SWITCH REQUEST ACKNOWLEDGE message. -   12. Upon reception of the PATH SWITCH REQUEST ACKNOWLEDGE message     from the AMF, the target gNB may send the UE CONTEXT RELEASE to     inform the source gNB about the success of the handover. The source     gNB may then release radio and C-plane related resources associated     to the UE context. Any ongoing data forwarding may continue.

In an example, the RRM configuration may include both beam measurement information (for layer 3 mobility) associated to SSB(s) and CSI-RS(s) for the reported cell(s) if both types of measurements are available. Also, if carrier aggregation (CA) is configured, the RRM configuration may include the list of best cells on each frequency for which measurement information is available. The RRM measurement information may also include the beam measurement for the listed cells that belong to the target gNB.

In an example, the common RACH configuration for beams in the target cell may be associated to the SSB(s). The network may have dedicated RACH configurations associated to the SSB(s) and/or may have dedicated RACH configurations associated to CSI-RS(s) within a cell. The target gNB may include one of the following RACH configurations in the Handover Command to enable the UE to access the target cell: Common RACH configuration; Common RACH configuration+Dedicated RACH configuration associated with SSB; Common RACH configuration+Dedicated RACH configuration associated with CSI-RS.

In an example, the dedicated RACH configuration may allocate RACH resource(s) together with a quality threshold to use them. When dedicated RACH resources are provided, they may be prioritized by the UE and the UE may not switch to contention-based RACH resources as long as the quality threshold of those dedicated resources is met. The order to access the dedicated RACH resources may be up to UE implementation.

In an example, the U-plane handling during the Intra-NR-Access mobility activity for UEs in RRC_CONNECTED may take the following principles into account to avoid data loss during HO: During HO preparation, U-plane tunnels may be established between the source gNB and the target gNB; During HO execution, user data may be forwarded from the source gNB to the target gNB; Forwarding may take place in order as long as packets are received at the source gNB from the UPF or the source gNB buffer has not been emptied. During HO completion: the target gNB may send a path switch request message to the AMF to inform that the UE has gained access and the AMF then may trigger path switch related 5GC internal signaling and actual path switch of the source gNB to the target gNB in UPF; the source gNB may continue forwarding data as long as packets are received at the source gNB from the UPF or the source gNB buffer has not been emptied.

In an example, in RRC_CONNECTED, the wireless device may measure multiple beams (at least one) of a cell and the measurement results (power values) may be averaged to derive the cell quality. In doing so, the UE may be configured to consider a subset of the detected beams. Filtering may take place at two different levels: at the physical layer to derive beam quality and then at RRC level to derive cell quality from multiple beams. Cell quality from beam measurements may be derived in the same way for the serving cell(s) and for the non-serving cell(s). Measurement reports may contain the measurement results of the X best beams if the UE is configured to do so by the gNB. An example measurement process is shown in FIG. 19.

A: measurements (beam specific samples) internal to the physical layer. Layer 1 filtering: internal layer 1 filtering of the inputs measured at point A. Exact filtering may be implementation dependent. A1: measurements (e.g., beam specific measurements) may be reported by layer 1 to layer 3 after layer 1 filtering. Beam Consolidation/Selection: beam specific measurements may be consolidated to derive cell quality. B: a measurement (e.g., cell quality) derived from beam-specific measurements may be reported to layer 3 after beam consolidation/selection. Layer 3 filtering for cell quality: filtering performed on the measurements provided at point B. C: a measurement after processing in the layer 3 filter. The reporting rate may be identical to the reporting rate at point B. This measurement may be used as input for one or more evaluation of reporting criteria. Evaluation of reporting criteria: may check whether actual measurement reporting is necessary at point D. The evaluation may be based on more than one flow of measurements at reference point C e.g., to compare between different measurements. This is illustrated by input C and C1. The UE may evaluate the reporting criteria at least every time a new measurement result is reported at point C, C1. D: measurement report information (message) sent on the radio interface. L3 Beam filtering: filtering performed on the measurements (e.g., beam specific measurements) provided at point A1. E: a measurement (e.g., beam-specific measurement) after processing in the beam filter. The reporting rate may be identical to the reporting rate at point A1. This measurement may be used as input for selecting the X measurements to be reported. Beam Selection for beam reporting: may select the X measurements from the measurements provided at point E. F: beam measurement information included in measurement report (sent) on the radio interface.

In an example, measurement reports may be characterized by the following: measurement reports may include the measurement identity of the associated measurement configuration that triggered the reporting; cell and beam measurement quantities to be included in measurement reports may be configured by the network; the number of non-serving cells to be reported may be limited through configuration by the network; cells belonging to a blacklist configured by the network may not be used in event evaluation and reporting, and conversely when a whitelist is configured by the network, only the cells belonging to the whitelist may be used in event evaluation and reporting; Beam measurements to be included in measurement reports may be configured by the network.

In an example, intra-frequency neighbor (cell) measurements and inter-frequency neighbor (cell) measurements may be defined as follows: SSB based intra-frequency measurement: a measurement is defined as an SSB based intra-frequency measurement provided the center frequency of the SSB of the serving cell and the center frequency of the SSB of the neighbor cell are the same, and the subcarrier spacing of the two SSBs may also be the same. SSB based inter-frequency measurement: a measurement may be defined as an SSB based inter-frequency measurement provided the center frequency of the SSB of the serving cell and the center frequency of the SSB of the neighbor cell are different, or the subcarrier spacing of the two SSBs is different. For SSB based measurements, one measurement object may correspond to one SSB and the UE may consider different SSBs as different cells. CSI-RS based intra-frequency measurement: a measurement may be defined as a CSI-RS based intra-frequency measurement provided the bandwidth of the CSI-RS resource on the neighbor cell configured for measurement is within the bandwidth of the CSI-RS resource on the serving cell configured for measurement, and the subcarrier spacing of the two CSI-RS resources is the same. CSI-RS based inter-frequency measurement: a measurement may be defined as a CSI-RS based inter-frequency measurement provided the bandwidth of the CSI-RS resource on the neighbor cell configured for measurement is not within the bandwidth of the CSI-RS resource on the serving cell configured for measurement, or the subcarrier spacing of the two CSI-RS resources may be different.

In an example, whether a measurement is non-gap-assisted or gap-assisted may depend on the capability of the UE, the active BWP of the UE and the current operating frequency: For SSB based inter-frequency, a measurement gap configuration may be provided in the following cases: If the UE only supports per-UE measurement gaps; If the UE supports per-FR measurement gaps and any of the configured BWP frequencies of any of the serving cells are in the same frequency range of the measurement object. For SSB based intra-frequency measurement, a measurement gap configuration may be provided in the following case: Other than the initial BWP, if any of the UE configured BWPs do not contain the frequency domain resources of the SSB associated to the initial DL BWP.

In an example, in non-gap-assisted scenarios, the UE may be able to carry out such measurements without measurement gaps. In gap-assisted scenarios, the UE may not be assumed to be able to carry out such measurements without measurement gaps.

In an example, an IE MeasConfig may specify measurements to be performed by the UE, and may cover intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps. A parameter measGapConfig may be used to setup and release measurement gaps in NR. A parameter measIdToAddModList may indicate a list of measurement identities to add and/or modify. A parameter measIdToRemoveList may indicate a list of measurement identities to remove. A parameter measObjectToAddModListmay indicate a list of measurement objects to add and/or modify. A parameter reportConfigToAddModList may indicate a list of measurement reporting configurations to add and/or modify. A parameter reportConfigToRemoveList may indicate a list of measurement reporting configurations to remove. A parameter s-MeasureConfig may indicate a threshold for NR SpCell RSRP measurement controlling when the UE is required to perform measurements on non-serving cells. Choice of ssb-RSRP corresponds to cell RSRP based on SS/PBCH block and choice of csi-RSRP corresponds to cell RSRP of CSI-RS. A parameter measGapSharingConfig may specify the measurement gap sharing scheme and controls setup/release of measurement gap sharing.

In an example, an IE MeasId may be used to identify a measurement configuration, e.g., linking of a measurement object and a reporting configuration.

In an example, an IE MeasIdToAddModList may concern a list of measurement identities to add or modify, with for each entry the measId, the associated measObjectId and the associated reportConfigId. In an example, an IE MeasObjectId may be used to identify a measurement object configuration.

In an example, an IE MeasObjectNR may specify information applicable for SS/PBCH block(s) intra/inter-frequency measurements and/or CSI-RS intra/inter-frequency measurements. A parameter cellIndividualOffset may indicate cell individual offsets applicable to a specific cell. A parameter physCellId may indicate physical cell identity of a cell in the cell list. A parameter absThreshCSI-RS-Consolidation may indicate absolute threshold for the consolidation of measurement results per CSI-RS resource(s) from L1 filter(s). The field may be used for the derivation of cell measurement results and the reporting of beam measurement information per CSI-RS resource. A parameter absThreshSS-BlocksConsolidation may indicate absolute threshold for the consolidation of measurement results per SS/PBCH block(s) from L1 filter(s). The field may be used for the derivation of cell measurement results and the reporting of beam measurement information per SS/PBCH block index. A parameter blackCellsToAddModList may indicate a list of cells to add/modify in the blacklist of cells. It may apply to SSB resources. A parameter blackCellsToRemoveList may indicate a list of cells to remove from the blacklist of cells. A parameter cellsToAddModList may indicate a list of cells to add/modify in the cell list. A parameter cellsToRemoveList may indicate a list of cells to remove from the cell list. A parameter freqBandIndicatorNR may indicate a frequency band in which the SSB and/or CSI-RS indicated in this MeasObjectNR may be located and according to which the UE may perform the RRM measurements. This field may be provided when the network configures measurements with this MeasObjectNR. A parameter measCycleSCell may be used when an SCell is configured on the frequency indicated by the measObjectNR and is in deactivated state. gNB may configure the parameter whenever an SCell is configured on the frequency indicated by the measObjectNR. The field may also be signalled when an SCell is not configured. A parameter nrofCSInrofCSI-RS-ResourcesToAverage may indicate the maximum number of measurement results per beam based on CSI-RS resources to be averaged. The same value applies for each detected cell associated with this MeasObjectNR. A parameter offsetMO may indicate values applicable to all measured cells with reference signal(s) indicated in this MeasObjectNR. A parameter quantityConfigIndex may indicate the n-th element of quantityConfigNR-List provided in MeasConfig. A parameter referenceSignalConfig may indicate RS configuration for SS/PBCH block and CSI-RS. A parameter refFreqCSI-RS may indicate point A which may be used for mapping of CSI-RS to physical resources. A parameter ssbFrequency may indicate the frequency of the SS associated to this MeasObjectNR. A parameter ssbSubcarrierSpacing may indicate subcarrier spacing SSB. A parameter whiteCellsToAddModList may indicate list of cells to add/modify in the white list of cells. It may apply to SSB resources. A parameter whiteCellsToRemoveList may indicate a list of cells to remove from the whitelist of cells.

In an example, an IE MeasObjectToAddModList may concern a list of measurement objects to add or modify. In an example, an IE MeasResults may cover measured results for intra-frequency, inter-frequency, and inter-RAT mobility.

In an example, a handover preparation procedure may be used to establish necessary resources in an NG-RAN node for an incoming handover. The procedure may use UE-associated signaling. An example procedure is shown in FIG. 20.

In an example, the source NG-RAN node may initiate the procedure by sending the HANDOVER REQUEST message to the target NG-RAN node. When the source NG-RAN node sends the HANDOVER REQUEST message, it may start a timer TXnRELOCprep.

In an example, if the target NG-RAN node does not admit at least one PDU session resource, or a failure occurs during the Handover Preparation, the target NG-RAN node may send the HANDOVER PREPARATION FAILURE message to the source NG-RAN node. An example procedure is shown in FIG. 21. The message may contain the Cause IE with an appropriate value.

In an example, if there is no response from the target NG-RAN node to the HANDOVER REQUEST message before timer TXnRELOCprep expires in the source NG-RAN node, the source NG-RAN node may cancel the Handover Preparation procedure towards the target NG-RAN node by initiating the Handover Cancel procedure with the appropriate value for the Cause IE. The source NG-RAN node may ignore a HANDOVER REQUEST ACKNOWLEDGE or HANDOVER PREPARATION FAILURE message received after the initiation of the Handover Cancel procedure and may remove reference and release resources related to the concerned Xn UE-associated signaling.

In an example, a Handover Cancel procedure is used to enable a source NG-RAN node to cancel an ongoing handover preparation or an already prepared handover. An example is shown in FIG. 22. The procedure may use UE-associated signaling. In an example, the source NG-RAN node initiates the procedure by sending the HANDOVER CANCEL message to the target NG-RAN node. The source NG-RAN node shall indicate the reason for cancelling the handover by means of an appropriate cause value. In an example, if the HANDOVER CANCEL message refers to a context that does not exist, the target NG-RAN node may ignore the message.

In an example, a handover request message may be sent by the source NG-RAN node to the target NG-RAN node to request the preparation of resources for a handover. The handover request message may comprise the following IEs and IE Groups: Message Type, Source NG-RAN node UE XnAP ID reference, Cause, Target Cell Global ID, GUAMI, UE Context information, Trace Activation, Masked IMEISV, UE History Information and UE Context Reference at the S-NG-RAN node.

The UE Context Information may comprise following IEs: NG-C UE associated Signaling reference, Signaling TNL association address at source NG-C side, UE Security Capabilities, AS Security Information, Index to RAT/Frequency Selection Priority, UE Aggregate Maximum Bit Rate, PDU Session Resources To Be Setup List, RRC Context, Location Reporting Information and Mobility Restriction List.

The UE Context Reference at the S-NG-RAN node may comprise Global NG-RAN Node ID and S-NG-RAN node UE XnAP ID.

The Message Type IE uniquely identifies the message being sent. The Message Type IE may include a Procedure Code field and a Type of Message field. The type of Message field may comprise Initiating Message, Successful Outcome and Unsuccessful Outcome. The NG-RAN node UE XnAP ID may uniquely identify a UE over the Xn interface within the NG-RAN node.

The purpose of the Cause IE may be to indicate the reason for a particular event for the XnAP protocol. In an example, the cause may be a Radio Network Layer cause. Example Radio Network Layer causes may include: Cell not Available, Handover Desirable for Radio Reasons, Handover Target not Allowed, Invalid AMF Set ID, No Radio Resources Available in Target Cell, Partial Handover, Reduce Load in Serving Cell, Resource Optimization Handover, Time Critical Handover, TXnRELOCoverall Expiry, TXnRELOCprep Expiry, Unknown GUAMI ID, Unknown Local NG-RAN node UE XnAP ID, Inconsistent Remote NG-RAN node UE XnAP ID, Encryption And/Or Integrity Protection Algorithms Not Supported, Protection Algorithms Not Supported, Multiple PDU Session ID Instances, Unknown PDU Session ID, Unknown QoS Flow ID, Multiple QoS Flow ID Instances, Switch Off Ongoing, Not supported 5QI value, TXnDCoverall Expiry, TXnDCprep Expiry, Action Desirable for Radio Reasons, Reduce Load, Resource Optimization, Time Critical action, Target not Allowed, No Radio Resources Available, Invalid QoS combination, Encryption Algorithms Not Supported, Procedure cancelled, RRM purpose, Improve User Bit Rate, User Inactivity, Radio Connection With UE Lost, Failure in the Radio Interface Procedure, Bearer Option not Supported, UP integrity protection not possible, UP confidentiality protection not possible, Resources not available for the slice(s), UE Maximum integrity protected data rate reason, CP Integrity Protection Failure, UP Integrity Protection Failure, Slice(s) not supported by NG-RAN, MN Mobility, SN Mobility, Count reaches max value, Unknown Old NG-RAN node UE XnAP ID, PDCP Overload, DRB ID not available, Unspecified, . . . , UE Context ID not known and Non-relocation of context.

In an example, the cause may be a Transport Layer cause. Example Transport Layer causes include: Transport Resource Unavailable, Unspecified, etc. In an example, the cause may be a Protocol Cause. Example Protocol causes may include Transfer Syntax Error, Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and Notify), Message not Compatible with Receiver State, Semantic Error, Abstract Syntax Error (Falsely Constructed Message), Unspecified, etc. Other examples of cause value may include Control Processing Overload, Hardware Failure, O&M Intervention, Not enough User Plane Processing Resources, Unspecified, etc.

The Target Cell Global ID IE may indicate an NR CGI or an E-UTRA CGI. The NR CGI IE may be used to globally identify an NR cell. The E-UTRA CGI may be used to globally identify an E_UTRA cell. An NG-C UE associated Signaling reference IE may be used to uniquely identify the UE association over the source side NG interface instance. A Signaling TNL association address at source NG-C side IE may be used to provide the transport layer information associated with NG or Xn control plane transport. A UE Security Capabilities IE may define the supported algorithms for encryption and integrity protection in the UE. An AS Security Information IE may be used to generate the key material to be used for AS security with the UE. An Index to RAT/Frequency Selection Priority IE may be used to define local configuration for RRM strategies such as camp priorities and control of inter-RAT/inter-frequency mobility in RRC_CONNECTED.

A UE Aggregate Maximum Bit Rate IE may be applicable for all Non-GBR QoS flows per UE which may be defined for the Downlink and the Uplink direction and a subscription parameter provided by the AMF to the NG-RAN. A PDU Session Resources To Be Setup List IE may contain PDU session resource related information used at UE context transfer between NG-RAN nodes. An RRC Context IE may include a HandoverPreparationInformation message. A Location Reporting Information IE may indicate how the location information may be reported. A Mobility Restriction List IE may define roaming or access restrictions for subsequent mobility actions for which the NR-RAN provides information about the target of the mobility action towards the UE, e.g., handover, or for SCG selection during dual connectivity operation or for assigning proper RNAs. If the NG-RAN receives the Mobility Restriction List IE, it may overwrite previously received restriction information.

A Trace Activation IE may define parameters related to a trace activation. A Masked IMEISV IE may contain IMEISV value with a mask, to identify a terminal model without identifying an individual Mobile Equipment. A Global NG-RAN Node ID IE may be used to globally identify an NG-RAN node. An S-NG-RAN node UE XnAP ID may uniquely identify a UE over the Xn interface within the NG-RAN node.

The HANDOVER RQUEST ACKNOWLEDGE message may be sent by the target NG-RAN node to inform the source NG-RAN node about the prepared resources at the target. The handover request message may comprise the following IEs and IE Group: Message Type; Source NG-RAN node UE XnAP ID; Target NG-RAN node UE XnAP ID; PDU Session Resources Admitted List; PDU Session Resources Not Admitted List; Target NG-RAN node To Source NG-RAN node Transparent Container; UE Context Kept Indicator; Criticality Diagnostics; and DRBs transferred to MN.

The Target NG-RAN node UE XnAP ID IE may uniquely identify a UE over the Xn interface within the NG-RAN node. The PDU Session Resources Admitted List IE may contain PDU session resource related information to report success of the establishment of PDU session resources. The PDU Session Resources Not Admitted List IE may indicate a list of PDU session resources which were not admitted to be added or modified. The Target NG-RAN node To Source NG-RAN node Transparent Container IE may include a HandoverCommand message.

The UE Context Kept Indicator IE may contain a list of PDU session resources which were not admitted to be added or modified. The Criticality Diagnostics IE may be sent by the NG-RAN node when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it may contain information about which IEs were not comprehended or were missing. The DRBs transferred to MN may contain a list of DRBs.

The Handover Preparation Failure message may be sent by the target NG-RAN node to inform the source NG-RAN node that the Handover Preparation has failed. The Handover Preparation Failure message may comprise following IEs: Message Type, Source NG-RAN node UE XnAP ID, Cause, and Criticality Diagnostics

The HandoverCommand message may be used to transfer the handover command as generated by the target gNB. The HandoverCommand may Contain the RRCReconfiguration message used to perform handover within NR or handover to NR, as generated (entirely) by the target gNB.

The HandoverPreparationInformation message may be used to transfer the NR RRC information used by the target gNB during handover preparation or UE context retrieval, e.g. in case of resume or re-establishment, including UE capability information. This message may be also used for transferring the information between the CU and DU. The direction of this message may be from source gNB/source RAN to target gNB or from CU to DU.

In an example, an as-Context IE may indicate local RAN context required by the target gNB or DU. An rrm-Config IE may indicate local RAN context used mainly for RRM purposes. A sourceConfig IE may indicate the radio resource configuration as used in the source cell. A ue-CapabilityRAT-List IE may indicate the UE radio access related capabilities concerning RATs supported by the UE. A ue-InactiveTime IE may indicate duration while UE has not received or transmitted any user data.

In an example, an rrcReconfiguration message may contain the RRCReconfiguration configuration as generated entirely by the MN. A sourceRB-SN-Config may contain the IE RadioBearerConfig as generated entirely by the SN. This field is only used in NE-DC and NR-DC. A sourceSCG-EUTRA-Config may contain the current dedicated SCG configuration in RRCConnectionReconfiguration message. A sourceSCG-NR-Config may contain the current dedicated SCG configuration in RRCReconfiguration message as generated entirely by the SN. In an example, the RRCReconfiguration message may include fields CellGroupConfig and measConfig.

In an example, a Mobility Restriction List IE may define roaming or access restrictions for subsequent mobility actions for which the NR-RAN provides information about the target of the mobility action towards the UE, e.g., handover, or for SCG selection during dual connectivity operation or for assigning proper RNAs. If the NG-RAN receives the Mobility Restriction List IE, it may overwrite previously received restriction information.

The purpose of the S-NG-RAN node Addition Preparation procedure may be to request the S-NG-RAN node to allocate resources for dual connectivity operation for a specific UE. The procedure may use UE-associated signaling. An example procedure is shown in FIG. 23. The M-NG-RAN node may initiate the procedure by sending the S-NODE ADDITION REQUEST message to the S-NG-RAN node. When the M-NG-RAN node sends the S-NODE ADDITION REQUEST message, it may start the timer TXn_(DCprep).

In an example, if the S-NG-RAN node admits at least one PDU session resource, the S-NG-RAN node may start the timer TXn_(DCoverall) when sending the S-NODE ADDITION REQUEST ACKNOWLEDGE message to the M-NG-RAN node. The reception of the S-NODE RECONFIGURATION COMPLETE message may stop the timer TXn_(DCoverall).

Upon receiving an S-NODE ADDITION REQUEST message containing the Desired Activity Notification Level IE, the S-NG-RAN node may, if supported, use this information to decide whether to trigger subsequent Activation Notification procedures according to the requested notification level.

In an example, if the S-NG-RAN node may not able to accept any of the bearers or a failure occurs during the S-NG-RAN node Addition Preparation, the S-NG-RAN node may send the S-NODE ADDITION REQUEST REJECT message with an appropriate cause value to the M-NG-RAN node. An example procedure is shown in FIG. 24.

In an example, an S-NODE ADDITION REQUEST message may be sent by the M-NG-RAN node to the S-NG-RAN node to request the preparation of resources for dual connectivity operation for a specific UE. The S-NODE ADDITION REQUEST message comprise following IEs and IE groups: Message Type, M-NG-RAN node UE XnAP ID, UE Security Capabilities, S-NG-RAN node Security Key, S-NG-RAN node UE Aggregate Maximum Bit Rate, Selected PLMN, Mobility Restriction List, Index to RAT/Frequency Selection Priority, PDU Session Resources To Be Added List, M-NG-RAN node to S-NG-RAN node Container, S-NG-RAN node UE XnAP ID, Expected UE Behavior, Requested Split SRBs, PCell ID, Desired Activity Notification Level, Available DRB IDs, S-NG-RAN node Maximum Integrity Protected Data Rate Uplink, S-NG-RAN node Maximum Integrity Protected Data Rate Downlink, Location Information at S-NODE reporting, MR-DC Resource Coordination Information, Masked IMEISV, NE-DC TDM Pattern, SN Addition Trigger Indication, Trace Activation and Requested Fast MCG recovery via SRB3. The PDU Session Resources To Be Added List may comprise following IEs: PDU Session ID, S-NSSAI, S-NG-RAN node PDU Session Aggregate Maximum Bit Rate, PDU Session Resource Setup Info—SN terminated and PDU Session Resource Setup Info—MN terminated.

The UE Security Capabilities IE may define the supported algorithms for encryption and integrity protection in the UE. The S-NG-RAN node Security Key IE may be used to apply security in the S-NG-RAN node. The selected PLMN IE may the PLMN identity. The Mobility Restriction List IE may define roaming or access restrictions for subsequent mobility actions for which the NR-RAN provides information about the target of the mobility action towards the UE, e.g., handover, or for SCG selection during dual connectivity operation or for assigning proper RNAs. If the NG-RAN receives the Mobility Restriction List IE, it may overwrite previously received restriction information. The Index to RAT/Frequency Selection Priority IE may be used to define local configuration for RRM strategies such as camp priorities and control of inter-RAT/inter-frequency mobility in RRC_CONNECTED. The PDU Session ID IE may identify PDU Session for a UE. The S-NSSAI IE may indicate Single Network Slice Selection Assistance Information (S-NSSAI). The S-NG-RAN node PDU Session Aggregate Maximum Bit Rate IE may be applicable for Non-GBR QoS flows per PDU session which may be defined for the downlink and the uplink direction and maybe provided at the Handover Preparation procedure to the target NG-RAN node and at the Retrieve UE Context procedure to the new NG-RAN node as received by the 5GC, during dual connectivity related procedures to the to the S-NG-RAN node as decided by the M-NG-RAN node. The PDU Session Resource Setup Info—SN terminated IE may contain information for the addition of S-NG-RAN node resources related to a PDU session for DRBs configured with an SN terminated bearer option. The M-NG-RAN node to S-NG-RAN node Container may include the ConfigInfo message.

The S-NG-RAN node UE XnAP ID may uniquely identify a UE over the Xn interface within the NG-RAN node. The Expected UE Behaviour IE may indicate the behaviour of a UE with predictable activity and/or mobility behaviour, to assist the NG-RAN node in determining the optimum RRC connection time and to help with the RRC_INACTIVE state transition and RNA configuration (e.g., size and shape of the RNA). The Requested Split SRBs may indicate that resources for Split SRBs are requested. The PCell ID IE may indicate an NR or an E-UTRA Cell Identity. The Desired Activity Notification Level IE may contain information on which level activity notification may be performed. The Available DRB IDs IE may indicate the list of DRB IDs that the S-NG-RAN node may use for SN-terminated bearers. The S-NG-RAN node Maximum Integrity Protected Data Rate Uplink IE and the S-NG-RAN node Maximum Integrity Protected Data Rate Downlink IE may indicate the number of bits delivered by NG-RAN in UL or to NG-RAN in DL within a period of time, divided by the duration of the period. It may be used, for example, to indicate the maximum or guaranteed bit rate for a GBR QoS flow, or an aggregate maximum bit rate. The Location Information at S-NODE reporting IE may indicate that the user's Location Information at S-NODE is to be provided. The MR-DC Resource Coordination Information may be used to coordinate resource utilization between the M-NG-RAN node and the S-NG-RAN node. The Masked IMEISV IE may contain the IMEISV value with a mask, to identify a terminal model without identifying an individual Mobile Equipment. The NE-DC TDM Pattern IE may be provided by the gNB and used by the ng-eNB to determine UL/DL reference configuration indicating the time during which a UE configured with NE-DC is allowed to transmit. The SN Addition Trigger Indication IE may indicate the trigger for S-NG-RAN node Addition Preparation procedure. The Trace Activation IE may define parameters related to a trace activation. The Requested Fast MCG recovery via SRB3 IE may indicate that the resources for fast MCG recovery via SRB3 are requested.

The S-NODE Addition Request Acknowledge message may be sent by the S-NG-RAN node to confirm the M-NG-RAN node about the S-NG-RAN node addition preparation.

The S-NODE Addition Request Acknowledge message may comprise following IEs and IE groups: Message Type, M-NG-RAN node UE XnAP ID, S-NG-RAN node UE XnAP ID, PDU Session Resources Admitted To Be Added List, PDU Session Resources Not Admitted List, S-NG-RAN node to M-NG-RAN node Container, Admitted Split SRBs, RRC Config Indication, Criticality Diagnostics, Location Information at S-NODE, MR-DC Resource Coordination Information, and Admitted fast MCG recovery via SRB3.

The S-NG-RAN node to M-NG-RAN node Container may include the CG-Config message. The Admitted Split SRBs IE may indicated admitted SRBs. The RRC Config Indication IE may indicate the type of RRC configuration used at the S-NG-RAN node.

The S-NODE ADDITION REQUEST REJECT message may be sent by the S-NG-RAN node to inform the M-NG-RAN node that the S-NG-RAN node Addition Preparation has failed. The S-NODE ADDITION REQUEST REJECT message may comprise following IEs: Message Type, M-NG-RAN node UE XnAP ID, S-NG-RAN node UE XnAP ID, Cause, and Criticality Diagnostics.

The purpose of the Xn Setup procedure may be to exchange application-level configuration data needed for two NG-RAN nodes to interoperate correctly over the Xn-C interface. The procedure may use non-UE-associated signaling. An example procedure is shown in FIG. 25. The NG-RAN node1 may initiate the procedure by sending the XN SETUP REQUEST message to the candidate NG-RAN node2. The candidate NG-RAN node2 may reply with the XN SETUP RESPONSE message. If the candidate NG-RAN node2 cannot accept the setup, it may respond with the XN SETUP FAILURE message with appropriate cause value.

The XN SETUP REQUEST message may be sent by a NG-RAN node to a neighboring NG-RAN node to transfer application data for an Xn-C interface instance.

The XN SETUP REQUEST message may comprise following IEs and IE groups: Message Type, Global NG-RAN Node ID, TAI Support List, AMF Region Information, List of Served Cells NR, List of Served Cells E-UTRA, Interface Instance Indication and TNL Configuration Info. The List of Served Cells NR may comprise a Served Cell Information NR IE, a Neighbor Information NR IE, a Neighbor Information E-UTRA, a Partial List Indicator and a Cell and Capacity Assistance Information IE.

The TAI Support List may indicate the list of tracking area identities (TAIs) supported by NG-RAN node and associated characteristics e.g., supported slices. The Served Cell Information NR IE may contain cell configuration information of an NR cell that a neighboring NG-RAN node may need for the Xn AP interface. The Neighbor Information NR IE may contain cell configuration information of NR cells that a neighbor NG-RAN node may need to properly operate its own served cells. The Cell and Capacity Assistance Information IE may be used by the NG-RAN node to request information about NR or E-UTRA cells and it includes information about cell list size capacity. The Interface Instance Indication IE may contain the subcarrier spacing, cyclic prefix and TDD DL-UL slot configuration of an NR cell that a neighbor NG-RAN node needs to take into account for cross-link interference mitigation, when operating its own cells. The NG-RAN node sending the list of Intended TDD DL-UL Configuration IEs includes into the list of the configurations of NR cells that are neighboring to the cells of the receiving NG-RAN node.

The XN SETUP RESPONSE message may be sent by a NG-RAN node to a neighboring NG-RAN node to transfer application data for an Xn-C interface instance. The XN SETUP FAILURE message may be sent by the neighboring NG-RAN node to indicate Xn Setup failure.

The usage scenarios for 5G may include enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and Ultra-Reliable and Low Latency communication (URLLC). A usage scenario that is located at the boundary between mMTC and URLLC may be time sensitive communication (TSC). The mMTC, URLLC and TSC may be associated with IoT use cases. In an example, eMBB, mMTC, URLLC and TSC use cases may be supported in the same network.

In an example, reduced capability wireless devices may support reduced number of UE RX/TX antennas, reduced UE Bandwidth, half-Duplex-FDD, relaxed UE processing time, and relaxed UE processing capability.

In an example, to enable UE power saving and battery lifetime enhancement for reduced capability UEs, the reduced capability UE may support reduced PDCCH monitoring by smaller numbers of blind decodes and CCE limits, extended DRX for RRC Inactive and/or Idle, and RRM relaxation for stationary devices.

In an example, the reduced capability UEs may support coverage recovery to compensate for potential coverage reduction due to the device complexity reduction.

Example embodiments may enable functionality that may allow devices with reduced capabilities to be explicitly identifiable to networks and network operators, and allow operators to restrict their access, if desired.

Reduced capability wireless devices may have lower complexity such as reduced number of TX/RX antennas, reduced UE Bandwidth, half-Duplex-FDD, relaxed UE processing time, and relaxed UE processing capability. Operation of reduced capability wireless devices in a wireless network may degrade the performance (e.g., in terms of throughput, latency, etc.) of normal (e.g., non-reduced capability) wireless devices. There is a need to enhance existing solutions (e.g., signaling and processes) for handover and dual connectivity of wireless devices with reduced capability. Example embodiments enhance existing processes and signaling for handover and dual connectivity of wireless devices with reduced capability.

In an example, a wireless device may be served by a cell of first base station. The wireless device may be a first type wireless device. For example, the wireless device may be a reduced capability wireless device. The cell may be a primary cell. In an example, the wireless device may be configured with and may communicate with the first base station on one cell. In an example, the wireless device may be configured with a plurality of cells (e.g., in case of carrier aggregation) and the cell may be a primary cell. In an example, the first base station may initiate a Handover preparation procedure to a second base station to establish necessary resources for an incoming handover. In case of a successful handover, the primary cell for the wireless device may change from the cell of the first base station to a first cell of the second base station.

In an example embodiment as shown in FIG. 26, a first base station may initiate a Handover preparation procedure for a wireless device to a second base station. In an example, the first base station may determine a first cell of the second base station as a target cell for the handover procedure. The first base station may determine the first cell of the second base station as the target cell based on measurement information/results/report received by the first base station from the wireless device. For example, the first base station may transmit measurement configuration parameters to the wireless device. The measurement configuration parameters may indicate reference signals (e.g., radio resources of the reference signals) for wireless device measurements. The reference signals may comprise CSI-RS and/or SSB. The wireless device may measure the references signals and may determine the measurement information/results/reports. The wireless device may measure received signal strength/RSSI/RSRP of the reference signals from one or more cells (e.g., neighboring cells of the first base station or neighboring base stations). The wireless device may transmit the measurement information/results/report to the first base station via RRC signaling using a measurement reporting procedure.

The first base station may start the Handover preparation procedure based on transmitting a handover request message to the second base station. The handover request message may indicate that the handover request is for the first cell of the second base station. In an example, the handover request message may comprise an information element indicating a global identifier of the first cell of the second base station as the target cell for the handover procedure.

The handover request message may comprise a first information element. A value of the first information element may indicate that the handover request is for a wireless device of a first type. For example, the first information element may indicate that the handover request is for a wireless device with reduced capability. In an example, the first information element may take a plurality of values, each value of the plurality of values corresponding to a wireless device type. The plurality of values may comprise a value indicating that the handover request is for a wireless device of first type (e.g., reduced capability).

The wireless devices of the first type may not be admitted by the first cell of the second base station. In an example, the wireless devices of the first type may not be admitted by the second base station. For example, the first cell of the second base station may serve wireless devices that are not reduced-capability wireless devices. For example, the second base station may serve wireless devices that are not reduced-capability wireless devices. For example, the second base station may have a type and the type of the second base station may indicate that the second base station does not admit wireless devices of the first type.

Based on the wireless devices of the first type not being admitted by the first cell of the second base station, the second base station may transmit a handover preparation failure message to the first base station. In an example, based on the wireless devices of the first type not being admitted by the second base station, the second base station may transmit a handover preparation failure message to the first base station. The handover preparation failure message may indicate that the handover preparation has failed. The handover preparation failure message may indicate that the wireless device is not admitted by the second base station. In an example, the handover preparation failure message may indicate that the wireless device is not admitted by the first cell of the second base station. The handover preparation failure message may comprise a cause IE, a value of the cause IE indicating that the cause of the handover preparation failure. The value of the cause IE may indicate that the cause of the handover preparation failure is that the wireless devices of the first type are not admitted by the first cell of the second base station. In an example, the value of the cause IE may indicate that the cause of the handover preparation failure is that the wireless devices of the first type are not admitted by the second base station. For example, the value of the cause IE may indicate that the type of the second base station does not allow wireless devices of the first type.

In an example embodiment as shown in FIG. 27, a wireless device may be a first type wireless device. In an example, the first type wireless device may be a reduced capability wireless device. The wireless device may receive, from a first base station, one or more messages comprising configuration parameters. The one or more messages may comprise one or more RRC messages. The one or more messages may comprise measurement configuration parameters. The measurement configuration parameters may indicate reference signals (e.g., radio resources of reference signals) for a measurement procedure. The wireless device may use the measurement configuration parameters for the measurement procedure and for measurement reporting. The reference signals may comprise SSB and/or CSI-RS. The measurement configuration parameters may indicate identifiers of one or more cells. The wireless device may measure signal strength/RSSI/RSRP of reference signals associated with the indicated one or more cells and based on the measurement configuration parameters.

The wireless device may transmit the measurement information/results/report to the first base station based on the measurement configuration parameters. The wireless device may transmit the measurement report using one or more RRC messages. The measurement report may comprise measurement information associated with the one or more cells indicated by the measurement configuration parameters for measuring signal strengths of the corresponding reference signals. The one or more cells may comprise a first cell of a second base station and the measurement report may comprise first information/results associated with the first cell of the second bae station.

In an example, the first base station may initiate a handover preparation procedure based on the measurement report received from the wireless device. The first base station may transmit a Handover request message to the second base station to establish necessary resources for an incoming handover. The handover request message may indicate that the handover request is for the first cell of the second base station. For example, the handover request message may comprise an information element indicating a global identifier of the first cell of the second base station. The handover request message may comprise a first information element, a value of the first information element indicating that the handover request is for a first type wireless device (e.g., a reduced capability wireless device).

In an example, the first information element in the handover request message, indicating that the handover request is for the first type wireless device, may be a cause information element. A cause value of the cause information element may indicate that the handover request is for a wireless device of a first type (e.g., reduced capability wireless device). For example, the cause value may indicate that the first base station is offloading the wireless devices of the first type to the second base station. For example, the cause value may indicate that a first number of wireless devices of the first type (e.g., reduced capability wireless devices) served by the first base station (e.g., on a cell of the first base station or the aggregate number of wireless devices of the first type served by the first base station) reaching a threshold. For example, the cause value may indicate that the first base station is discontinuing serving wireless devices of the first type (e.g., reduced capability wireless devices). For example, the cause value may indicate that the first base station is discontinuing serving wireless devices of the first type (e.g., reduced capability wireless devices) on a cell of the first base station (e.g., the cell on which the wireless device is currently being served by the first base station).

In an example, the first information element may be a wireless device identifier IE, a value of the wireless device identifier IE indicating that the wireless device is a first type wireless device. For example, the wireless device identifier IE may be a Source NG-RAN node UE XnAP ID reference. The Source NG-RAN node UE XnAP ID reference may be allocated at the first base station and may uniquely identify the wireless device over the Xn interface.

In an example, the first information element may take a plurality of values. A value in the plurality of values may indicate a wireless device in a plurality of wireless device types.

In an example, the handover request message may comprise an RRC context including a handover preparation information message. The handover preparation information message may comprise the first information element indicating the wireless device type (e.g., indicating that the wireless device is a first type wireless device, e.g., reduced capability wireless device). For example, the handover preparation information message may comprise at least one of the UE capability RAT container list IE, source Config IE, RRM config IE and access stratum (AS) config IE. At least one of the UE capability RAT container list IE, source Config IE, RRM config IE and access stratum (AS) config IE may comprise the first information element. For example, the source config IE may comprise the first information element. For example, the AS config may comprise the first information element.

The handover request message may comprise a mobility restriction IE. In an example, the mobility restriction IE may comprise the first IE. For example, the first information element may indicate that the handover request is for a first type wireless device and that the second base station may consider one or more restriction parameters associated with the first type wireless devices (e.g., reduced capability wireless devices). The one or more parameters may be used by the second base station to admit or not admit the wireless device. The one or more parameters may comprise a threshold number of wireless devices coexisting with the wireless device of the first type, etc.

The wireless devices of the first type (e.g., reduced capability wireless devices) may be admitted/admissible on the first cell of the second base station. For example, the wireless devices of the first type (e.g., reduced capability wireless devices) may coexist, on the first cell of the second base station, with wireless devices that are not of the first type (e.g., wireless devices that are not reduced capability wireless devices). In an example, the wireless devices of the first type (e.g., reduced capability wireless devices) may be admitted/admissible by the second base station. For example, a type of the second base station may allow admitting wireless devices of the first type.

The second base station may transmit a handover request acknowledge message to the first base station in response to the handover request message and based on the wireless devices of the first type (e.g., reduced capability wireless device) being admitted on the first cell of the second base station. In an example, the second base station may transmit a handover request acknowledge message to the first base station in response to the handover request message and based on the wireless devices of the first type (e.g., reduced capability wireless device) being admitted by the second base station (e.g., a type of the second base station allowing wireless devices of the first type, e.g., reduced capability wireless devices). The second base station may determine that the wireless device is of the first type (e.g., reduced capability wireless device) based on the first information element in the handover request message. The second base station may determine that the wireless device is admitted on the first cell of the second base station based on the wireless devices of the first type being admitted/admissible on the first cell of the second base station and/or by the second base station. The handover request message may comprise a transparent container comprising the handover command message and the handover command may comprise an RRC reconfiguration message.

The first base station may transmit the RRC reconfiguration message/handover command to the wireless device. The RRC reconfiguration message may comprise configuration parameters of the first cell of the second base station. The RRC reconfiguration message comprise one or more parameters for a random access process by the wireless device on the first cell of the second base station.

The wireless device may perform a random access procedure by transmitting a random access preamble on the first cell of the second base station. The wireless device may receive an uplink grant on the first cell of the second base station based on the random access procedure. For example, the wireless device may receive the uplink grant in a random access response. For example, the wireless device may receive the uplink grant based om downlink control information received in a downlink control channel. The wireless device may transmit an RRC reconfiguration complete message to the second base station based on the uplink grant. The RRC reconfiguration complete message may be used to confirm the successful completion of an RRC connection reconfiguration.

In an example, a wireless device may be served by one or more cells of a first base station. The wireless device may be a first type wireless device. For example, the wireless device may be a reduced capability wireless device. The first base station may determine to configure one or more cells of another base station to allocate resources for dual connectivity operation of the wireless device. The first base station may determine to configure the one or more cells of the other base station based on downlink data requirements and/or uplink data requirements (e.g., based on buffer status reports transmitted by the wireless device). The first base station may initiate an S-NG-RAN node Addition Preparation procedure for a second base station to request the second base station to allocate resources for dual connectivity operation for the wireless device. With the dual connectivity operation, the wireless device may be configured with a master cell group (MCG) comprising one or more first cells for communication of the wireless device with the first base station and a secondary cell group (SCG) comprising one or more second cells for communication of the wireless device with the second base station.

In an example embodiment as shown in FIG. 28, a first base station may transmit an S-NODE addition request message to the second base station. The first base station may transmit the S-NODE addition request message for dual connectivity operation of the wireless device. The S-NODE addition request message may comprise a first information element, a value of the first information element indicating that the wireless device is the first type wireless device (e.g., reduced capability wireless device). The second base station may determine that the wireless device is the first type wireless device based on the value of the information element.

In an example, the first information element may indicate a wireless device identifier. The wireless device identifier may indicate a wireless device type. In an example, the first information element may be a M-NG-RAN node UE XnAP ID IE. The M-NG-RAN node UE XnAP ID IE may be allocated at the M-NG-RAN node (first base station). In an example, the first information element may be a S-NG-RAN node UE XnAP ID IE. The S-NG-RAN node UE XnAP ID IE may be allocated at the S-NG-RAN node (second base station). The NG-RAN node UE XnAP ID may uniquely identify a UE over the Xn interface within the NG-RAN node (base station). For example, a value of the M-NG-RAN node UE XnAP ID IE or a value of the S-NG-RAN node UE XnAP ID IE may indicate that the wireless device is a first type wireless device (e.g., a reduced capability wireless device).

The S-NODE addition request message may comprise a mobility restriction IE. In an example, the mobility restriction IE may comprise the first IE. For example, the first information element may indicate that the S-NODE addition request is for a first type wireless device and that the second base station may consider one or more restriction parameters associated with the first type wireless devices (e.g., reduced capability wireless devices). The one or more parameters may be used by the second base station to admit or not admit the wireless device. The one or more parameters may comprise a threshold number of wireless devices coexisting with the wireless device of the first type, etc.

The S-NODE addition request message may comprise an expected UE behavior IE. For example, the expected behavior IE may indicate the behavior of a wireless device with predictable activity and/or mobility behavior, to assist the NG-RAN node in determining the optimum RRC connection time. In an example, the expected UE behavior IE may comprise the first information element indicating the wireless device type.

The wireless devices of the first type (e.g., reduced capability wireless devices) may be admitted/admissible on the one or more cells of the second base station. For example, the wireless devices of the first type (e.g., reduced capability wireless devices) may coexist, on the one or more cells of the second base station, with wireless devices that are not of the first type (e.g., wireless devices that are not reduced capability wireless devices). In an example, the wireless devices of the first type (e.g., reduced capability wireless devices) may be admitted/admissible by the second base station. For example, a type of the second base station may allow admitting wireless devices of the first type.

The second base station may transmit an S-NODE addition request acknowledge message in response to the S-NODE addition request message and based on the wireless devices of the first type being admitted by the one or more cells of the second base station. The S-NODE addition request acknowledge message may comprise an M-NG-RAN node to S-NG-RAN node Container comprising a cell group configuration (CG-Config) IE. The CG-Config IE may be used to transfer the SCG radio configuration as generated by the second base station (SgNB). The CG-Config may comprise a scg-CellGroupConfig IE comprising an RRCReconfiguration message. The RRCReconfiguration message may be sent to the wireless device and may be used upon SCG establishment or modification, as generated by the second base station (SgNB).

The first base station may transmit configuration parameters of a secondary cell group (SCG) to the wireless device. The first base station may transmit the configuration parameters of the SCG to the wireless device based on receiving the S-NODE addition request acknowledge message from the second base station. The configuration parameters of the secondary cell group may be based on the CG-Config IE included in the S-NODE addition request message. For example, the CG-Config may be included in the M-NG-RAN node to S-NG-RAN node Container and the first base station may transmit the CG-Config IE included in the container to the wireless device.

In an example embodiment as shown in FIG. 29, a first base station may transmit an S-NODE addition request message to the second base station. The S-NODE addition request message may indicate a request for dual connectivity operation for a wireless device. The S-NODE addition request message may comprise a first information element indicating that the request for S-NODE addition is for a wireless device of a first type (e.g., a reduced capability wireless device).

In an example, the first information element may indicate a wireless device identifier. The wireless device identifier may indicate a wireless device type. In an example, the first information element may be a M-NG-RAN node UE XnAP ID IE. The M-NG-RAN node UE XnAP ID IE may be allocated at the M-NG-RAN node (first base station). In an example, the first information element may be a S-NG-RAN node UE XnAP ID IE. The S-NG-RAN node UE XnAP ID IE may be allocated at the S-NG-RAN node (second base station). The NG-RAN node UE XnAP ID may uniquely identify a UE over the Xn interface within the NG-RAN node (base station). For example, a value of the M-NG-RAN node UE XnAP ID IE or a value of the S-NG-RAN node UE XnAP ID IE may indicate that the wireless device is a first type wireless device (e.g., a reduced capability wireless device).

In an example, the S-NODE addition request message may comprise a mobility restriction IE. In an example, the mobility restriction IE may comprise the first IE. For example, the first information element may indicate that the S-NODE addition request is for a first type wireless device and that the second base station may consider one or more restriction parameters associated with the first type wireless devices (e.g., reduced capability wireless devices). The one or more parameters may be used by the second base station to admit or not admit the wireless device. The one or more parameters may comprise a threshold number of wireless devices coexisting with the wireless device of the first type, etc.

In an example, the S-NODE addition request message may comprise an expected UE behavior IE. For example, the expected behavior IE may indicate the behavior of a wireless device with predictable activity and/or mobility behavior, to assist the NG-RAN node in determining the optimum RRC connection time. In an example, the expected UE behavior IE may comprise the first information element indicating the wireless device type.

The wireless devices of the first type (e.g., reduced capability wireless devices) may not be admitted/admissible on a cell of the second base station. In an example, the wireless devices of the first type (e.g., reduced capability wireless devices) may not be admitted/admissible by the second base station. For example, a type of the second base station may not allow admitting wireless devices of the first type (e.g., reduced capability wireless devices).

Based on the wireless devices of the first type (e.g., reduced capability wireless devices) not being admitted on a cell of the second base station or by the second base station, the second base station may transmit a S-NODE addition request reject message to the first base station. In an example, the S-NODE addition request reject message may comprise a cause value indicating that the wireless devices of the first type (e.g., reduced capability wireless devices) are not admitted/admissible by the second base station and/or on a cell of the second base station.

In an example, a first base station may receive an application protocol message (e.g., an Xn Setup message) from a second base station. The application protocol message may comprise one or more information elements indicating information about wireless devices of the first type (e.g., reduced capability wireless devices). For example, the information about the wireless devices of the first type may comprise a number of the wireless devices of the first type served by a cell of the second base station. For example, the information about the wireless devices of the first type may comprise an indication on whether the second base station serves a wireless device of the first type (e.g., reduced capability wireless device). For example, the information about the wireless devices of the first type may comprise an indication on whether the second base station serves a wireless device of the first type via a cell of the second base station. For example, the information about the wireless devices of the first type may indicate whether the second base station admits wireless devices of the first type. For example, the information about the wireless devices of the first type may indicate whether the second base station admits wireless devices of the first type on a cell of the second base station.

In an example embodiment as shown in FIG. 30, the first base station may transmit a handover request message, to the second base station, based on the information about the wireless devices of the first type transmitted by the second base station and received by the first base station. For example, the information about the wireless devices of the first type may indicate that the second base station admits wireless devices of the first type on a cell of the second base station. The transmitting the handover request message may be based on the information about the wireless devices of the first type indicating that the second base station admits wireless devices of the first type on a cell of the second base station. For example, the information about the wireless devices of the first type may indicate a number of the wireless devices of the first type served by a cell of the second base station. The transmitting the handover request message may be based on the number of the wireless devices of the first type served by a cell of the second base station. For example, the information about the wireless devices of the first type may comprise an indication on whether the second base station serves a wireless device of the first type. The transmitting the handover request message may be based on the indication.

Based on the wireless device being admitted by the second base station, the second base station may transmit a handover request acknowledge message to the first base station. The handover request acknowledge message may comprise an RRC reconfiguration message comprising configuration parameters of the handover target cell of the second base station. The first base station may transmit the RRC reconfiguration message to the wireless device. The wireless device may transmit an RRC reconfiguration completer message to the second base station.

In an example embodiment as shown in FIG. 31, the first base station may transmit an S-NODE addition request message based on the information about the wireless devices of the first type transmitted by the second base station and received by the first base station. For example, the information about the wireless devices of the first type may indicate that the second base station admits wireless devices of the first type on a cell of the second base station. The transmitting the S-NODE addition request message may be based on the information about the wireless devices of the first type indicating that the second base station admits wireless devices of the first type on a cell of the second base station. For example, the information about the wireless devices of the first type may indicate a number of the wireless devices of the first type served by a cell of the second base station. The transmitting the S-NODE addition request message may be based on the number of the wireless devices of the first type served by a cell of the second base station. For example, the information about the wireless devices of the first type may comprise an indication on whether the second base station serves a wireless device of the first type. The transmitting the S-NODE addition request message may be based on the indication.

Based on the wireless device being admitted by the second base station, the second base station may transmit a S-NODE addition request acknowledge message to the first base station. The S-NODE addition request acknowledge message may comprise a cell group configuration (CG-Config) IE comprising configuration parameters of a cell group. The first base station may transmit configuration parameters of secondary cell group to the wireless device, wherein the configuration parameters of the secondary cell group may be based on the CG-Config IE.

In an example embodiment, a first base station may transmit to a second base station a handover request message, wherein the handover request message: indicates a handover request to a first cell of the second base station; and comprises a first information element, a value of the first information element indicating that the handover request is for a wireless device of a first type. Based on wireless devices of the first type not being admitted on the first cell of the second base station, the first base station may receive a handover preparation failure message from the second base station. In an example, based on wireless devices of the first type not being admitted by the second base station, the first base station may receive a handover preparation failure message from the second base station.

In an example, the first type of the wireless device may be a reduced capability wireless device.

In an example, the handover preparation failure message may indicate that handover preparation has failed and/or the wireless device is not admitted on the first cell of the second base station. In an example, the handover preparation failure message may indicate that handover preparation has failed and/or the wireless device is not admitted by the second base station.

In an example, the handover preparation failure message may comprise a cause IE, a first cause value of the cause IE indicating that the wireless devices of the first type are not admitted on the first cell of the second base station. In an example, the handover preparation failure message may comprise a cause IE, a first cause value of the cause IE indicating that the wireless devices of the first type are not admitted by the second base station.

In an example, the handover request message may comprise an information element indicating a global identifier of the first cell of the second base station.

In an example, the first base station may receive from the wireless device, measurement information associated with the first cell of the second base station, wherein the handover request message is based on the measurement information. In an example, the first base station may transmit to the wireless device, measurement configuration parameters, wherein the measurement information is based on the measurement configuration parameters. In an example, the measurement configuration parameters may indicate reference signals; and the measurement information may be based on signal strength/RSSI/RSRP of the reference signals. In an example, the reference signals may comprise at least one of SSB and CSI-RS.

In an example embodiment, a wireless device, of a first type, may receive measurement configuration parameters from a first base station. The wireless device may transmit, based on measurement configuration parameters, measurement information comprising first information associated with a first cell of a second base station. The wireless device my receive, based on wireless devices of the first type being admitted on the first cell of the second base station, an RRC reconfiguration message comprising configuration parameters of the first cell of the second base station. In an example, the wireless device may receive, based on wireless devices of the first type being admitted by the second base station, an RRC reconfiguration message comprising configuration parameters of the first cell of the second base station. The wireless device may transmit an RRC reconfiguration complete message to the second base station.

In an example, the first type of the wireless device may be a reduced capability wireless device.

In an example, the receiving the RRC reconfiguration message may be based on a determination of the wireless device type at the second base station. The determination may be based on a first information element received by the second base station from the first base station. In an example, the first information element may be in a handover request message.

In an example, the wireless device may measure signal strength/RSSI of one or more reference signals based on the measurement configuration parameters. In an example, the one or more reference signals may comprise at least one of SSB and CSI-RS. In an example, the measurement information may be based on the signal strength/RSSI/RSRP of the one or more reference signals.

In an example, the RRC reconfiguration message may be in a handover request acknowledge message. In an example, the handover request acknowledge message may be received by the first base station from the second base station.

In an example embodiment, a first base station may transmit to a second base station, a handover request message, wherein the handover request message: may indicate a handover request to a first cell of the second base station; and may comprise a first information element, a value of the first information element indicating that the handover request is for a wireless device of a first type. Based on the wireless device of the first type being admitted on the first cell of the second base station, the first base station may receive from the second base station, a handover request acknowledge message comprising an RRC reconfiguration message. In an example, based on the wireless device of the first type being admitted by the second base station, the first base station may receive from the second base station, a handover request acknowledge message comprising an RRC reconfiguration message. The base station may transmit the RRC reconfiguration message to the wireless device.

In an example, the first type of the wireless device may be a reduced capability wireless device.

In an example, the handover request acknowledge message may comprise a transparent container comprising a handover command comprising the RRC reconfiguration message.

In an example, the RRC reconfiguration message may comprise configuration parameters of the first cell.

In an example, the first information element may be a cause information element, a cause value of the cause information element indicating that the handover request is for the wireless device of the first type. In an example, the cause value may indicate that the first base station is offloading the wireless devices of the first type to the second base station. In an example, the cause value may indicate that a first number of wireless devices of the first type, served by the first base station, reaching a threshold. In an example, the cause value may indicate that the first base station is discontinuing serving wireless devices of the first type.

In an example, the first information element may indicate a wireless device identifier indicating that the request for handover is for the wireless device of the first type.

In an example, the first information element may take a plurality of values, each value in the plurality of values corresponding to a wireless device type.

In an example, the handover request message may comprise an RRC context comprising the first information element. In an example, the RRC context may comprise at least one of the UE-CapabilityRAT-ContainerList, sourceConfig (AS-Config), RRM-Config and AS-Context. The at least one of the UE-CapabilityRAT-ContainerList, sourceconfig (AS-Config), RRM-Config and AS-Context may comprise the first information element.

In an example, the handover request message may comprise a handover preparation information message comprising the first information element. In an example, the handover preparation information may comprise at least one of the UE-CapabilityRAT-ContainerList, sourceConfig (AS-Config), RRM-Config and AS-Context. The at least one of the UE-CapabilityRAT-ContainerList, sourceconfig (AS-Config), RRM-Config and AS-Context may comprise the first information element.

In an example, the RRC context may comprise a sourceConfig (AS-Config) IE comprising the first information element. In an example, the handover preparation information message may comprise a sourceConfig (AS-Config) IE comprising the first information element.

In an example, the RRC context may comprise an AS Context information element comprising the first information element. In an example, the handover preparation information message may comprise an AS Context information element comprising the first information element.

In an example, the handover request message may comprise a mobility restriction list information element comprising the first information element.

In an example, the handover request message may comprise an information element indicating a global identifier of the first cell of the second base station.

In an example embodiment, a first base station may transmit to a second base station, an S-NODE addition request message indicating a request to allocate resources for dual connectivity operation for a wireless device, wherein the S-NODE addition request message comprises a first information element indicating that the request is for a wireless device of a first type. Based on the wireless device of the first type being admitted on one or more cells of the second base station, the first base station may receive from the second base station, an S-NODE addition request acknowledge message. The first base station may transmit to the wireless device, configuration parameters of a secondary cell group comprising the one or more cells.

In an example, the first type of the wireless device may be a reduced capability wireless device.

In an example, the first information element may indicate a wireless device identifier indicating that the request is for the wireless device of the first type.

In an example, the S-NODE addition request message may comprise a mobility restriction list information element comprising the first information element.

In an example, the S-NODE addition request message may comprise an expected UE behavior IE comprising the first information element.

In an example, the S-NODE addition request acknowledge message may comprise a cell group config (CG-Config) IE; and the configuration parameters of the secondary cell group is based on the cell group config IE.

In an example embodiment, a first base station may transmit to a second base station, an S-NODE addition request message indicating a request to allocate resources for dual connectivity operation for a wireless device. The S-NODE addition request message may comprise an information element indicating that the request is for a wireless device of a first type. Based on the wireless device of the first type not being admitted by the second base station, the first base station may receive an S-NODE addition request reject message from the second base station. In an example, based on the wireless device of the first type not being admitted on a cell of the second base station, the first base station may receive an S-NODE addition request reject message from the second base station.

In an example, the first type of the wireless device may be a reduced capability wireless device.

In an example, the S-NODE addition request reject message may comprise a cause value indicating that the wireless devices of the first type are not admitted.

In an example, the first information element may indicate a wireless device identifier indicating that the request is for the wireless device of the first type.

In an example, the S-NODE addition request message may comprise a mobility restriction list information element comprising the first information element.

In an example, the S-NODE addition request message may comprise an expected UE behavior IE comprising the first information element.

In an example embodiment, a first base station may receive from a second base station, an application protocol message (e.g., an Xn setup message) comprising one or more information elements indicating information about wireless devices of a first type. The first base station may transmit a handover request message to the second base station based on the information.

In an example embodiment, a first base station may receive from a second base station, an application protocol message (e.g., an Xn setup message) comprising one or more information elements indicating information about wireless devices of a first type. The first base station may transmit an S-NODE addition request message to the second base station based on the information.

In an example, the wireless devices of the first type may comprise wireless devices with reduced capability.

In an example, the information may comprise a number of wireless devices of the first type served by a cell of the second base station.

In an example, the information may comprise an indication on whether the second base station serves a wireless device of the first type (e.g., on a cell of the second base station).

In an example, the information may indicate whether the second base station admits wireless devices of the first type (e.g., on a cell of the second base station).

In an example, the information may indicate that the second base station admits wireless devices of the first type on a cell of the second base station. The transmitting the handover request message may be based on the information indicating that the second base station admits wireless devices of the first type on a cell of the second base station.

In an example, the information may indicate that the second base station admits wireless devices of the first type on a cell of the second base station. The transmitting the S-NODE addition request message may be based on the information indicating that the second base station admits wireless devices of the first type on a cell of the second base station.

In an example embodiment as shown in FIG. 32, a wireless device may be served by one or more cells of a first base station. The wireless device may be of a first type. For example, the wireless device may have reduced capabilities and may have a reduced capability type. In an example, a wireless device with reduced capability and with the reduced capability type may support reduced number of UE RX/TX antennas and/or reduced UE Bandwidth and/or half-Duplex-FDD and/or relaxed UE processing time and/or relaxed UE processing capability and/or reduced PDCCH monitoring by smaller numbers of blind decodes and CCE limits and/or extended DRX for RRC Inactive and/or Idle and/or and RRM relaxation.

The wireless device may receive, from the first base station, one or more messages (e.g., one or more RRC messages) comprising configuration parameters. The configuration parameters may comprise measurement configuration parameters. The configuration parameters may further comprise first configuration parameters of one or more reference signals. The one or more reference signals may comprise SSB and/or CSI-RS. The first configuration parameters of the one or more reference signals may indicate radio resources of the one or more reference signals. The wireless device may measure the one or more reference signals based on the measurement configuration parameters and based on the measurement configuration parameters. The wireless device may transmit to the first base station a measurement report comprising measurement information based on the measurement of the one or more reference signals. In an example, the wireless device may transmit the measurement report via an RRC message. The measurement information may include first information that is associated with a first cell of a second base station. For example, the first information may include signal strength (e.g., RSSI) of one or more reference signals (e.g., CSI-RS and/or SSB, etc.) associated with the first cell of the second base station. The transmission of the measurement report/measurement information to the first base station may be based on the measurement configuration parameters.

The first base station may determine a handover decision for handover of the wireless device to the second base station. In an example, the handover decision, by the first base station, may be based on receiving the measurement report/measurement information (including the first measurement information) from the wireless device. The first base station may initiate a handover preparation procedure in response to determination of the handover decision. The handover preparation procedure may be used to establish necessary resources in the second base station for an incoming handover. The first base station may transmit a handover request message to the second base station. The handover request message may indicate a request for handover of the wireless device to the first cell of the second base station. The handover request message may be used for preparation of resources for a handover.

The handover request message may further indicate that the wireless device is of a first type. The handover request message may comprise an indication indicating that the handover request is for the wireless device of the first type. For example, the handover request message may comprise one or more information elements indicating that the handover request is for the wireless device of the first type. In an example, the handover request message may comprise an RRC context field/IE. The RRC context field/IE, e.g., a handover preparation information message of the RRC context may comprise at least one of the UE-CapabilityRAT-ContainerList, sourceConfig (AS-Config), RRM-Config and AS-Context field/IEs. The least one of the UE-CapabilityRAT-ContainerList, sourceConfig (AS-Config), RRM-Config and AS-Context field/IEs may comprise the one or more information elements that indicate that the wireless device is of the first type. For example, an sourceConfig (AS-Config) field/IE of the RRC context (e.g., the handover preparation information message of the RRC context) may comprise the one or more information elements that indicate that the wireless device is of the first type. For example, an AS context field/IE of the RRC context (e.g., the handover preparation information message of the RRC context) may comprise the one or more information elements that indicate that the wireless device is of the first type. In an example, the handover request message may comprise a mobility restriction list information element comprising the one or more information elements that indicate that the wireless device is of the first type.

In an example, the handover request message may comprise an information element indicating a global identifier of the first cell of the second base station. The second base station may determine the target cell at the second base station for handover that the handover request is used for.

In an example, the one or more information elements, in the handover request message, comprise a cause information element with a value indicating that the handover request is for the wireless device of the first type. For example, the value of the cause information element may indicate that the first base station is offloading wireless devices of the first type to the second base station. For example, the value of the cause information element may indicate that a first number of wireless devices of the first type, served by the first base station, has reached a threshold. In an example, the threshold may have a pre-determined value. For example, the value of the cause information element may indicate that the first base station is discontinuing serving wireless devices of the first type. For example, the one or more information elements, of the handover request message, may indicate an identifier of the wireless device, wherein the identifier of the wireless device may indicate that the wireless device is of the first type. For example, a first information element in the handover request may take a plurality of values and a first value of the first information element may indicate that the wireless device is of the first type. In an example, a second value of the first information element may indicate that the wireless device is not of the first type or that the wireless device is of a second type (e.g., of a type without reduced capability).

The second base station may determine that the wireless device is of the first type based on the received handover request message, e.g., based on the indication of the wireless device type in the handover request message, e.g., based on the one or more information elements of the handover request message indicating that the handover request is for the wireless device of the first type. The second base station may admit (e.g., based on an admission control process) wireless devices of the first type. In an example, the second base station and/or the first cell of the second base station may admit (e.g., based on an admission control process) wireless devices of the first type. Based on the wireless devices of the first type being admitted by the second base station and based on the handover request message, the second base station may admit the wireless and the first base station may receive, from the second base station, a handover request acknowledge message. The handover request acknowledge message may comprise a transparent container comprising a handover command. The handover command may comprise an RRC reconfiguration message comprising configuration parameters of the first cell of the second base station. The first base station may transmit the handover command/the RRC reconfiguration message to the wireless device. In response to receiving the RRC reconfiguration message that includes the configuration parameters of the first cell of the second base station, the wireless device may establish a connection via the first cell of the second base station. For example, the wireless device may initiate a random access process on the first cell of the second base station (e.g., based on the random access configuration parameters of the configuration parameters of the first cell included in the RRC reconfiguration message). The wireless device may transmit an RRC reconfiguration complete message to the second base station. The RRC reconfiguration complete message may indicate successful completion of the RRC connection reconfiguration.

In accordance with various exemplary embodiments in the present disclosure, a device (e.g., a wireless device, a base station and/or alike) may include one or more processors and may include memory that may store instructions. The instructions, when executed by the one or more processors, cause the device to perform actions as illustrated in the accompanying drawings and described in the specification. The order of events or actions, as shown in a flow chart of this disclosure, may occur and/or may be performed in any logically coherent order. In some examples, at least two of the events or actions shown may occur or may be performed at least in part simultaneously and/or in parallel. In some examples, one or more additional events or actions may occur or may be performed prior to, after, or in between the events or actions shown in the flow charts of the present disclosure.

FIG. 33 shows an example flow diagram in accordance with several of various embodiments of the present disclosure. At 3310, a wireless device of a first type may receive, from a first base station, measurement configuration parameters. At 3320, the wireless device may transmit, based on the measurement configuration parameters, measurement information comprising first information associated with a first cell of a second base station. At 3330, the wireless device may receive, from the first base station a radio resource control (RRC) reconfiguration message comprising configuration parameters of the first cell, based on: an indication, from the first base station to the second base station, that the wireless device is of the first type; and wireless devices of the first type being admitted by the second base station. At 3340, the wireless device may transmit, to the second base station, an RRC reconfiguration complete message indicating successful completion of an RRC connection reconfiguration.

In an example embodiment, the first type of the wireless device may be a reduced capability wireless device.

In an example embodiment, the indication from the first base station to the second base station, at 3330, may be based on a message comprising one or more information elements indicating that the wireless device is of the first type. In an example embodiment, the message may be a handover request message indicating a request for preparation of resources for a handover.

In an example embodiment, the receiving the RRC reconfiguration message, at 3330, may be based on a determination of a type of the wireless device at the second base station. The determination may be based on one or more information elements received by the second base station from the first base station. In an example embodiment, the one or more information elements may be in a handover request message.

In an example embodiment, the wireless device may measure one or more reference signals based on the measurement configuration parameters received at 3310. In an example embodiment, the one or more reference signals may comprise at least one of synchronization signal block (SSB) and channel state information reference signal (CSI-RS). In an example embodiment, the wireless device may receive, from the first base station, first configuration parameters of the one or more reference signals. In an example embodiment, the first configuration parameters may indicate radio resources of the one or more reference signals.

FIG. 34 shows an example flow diagram in accordance with several of various embodiments of the present disclosure. At 3410, a first base station may transmit, to a second base station, a first message indicating: a handover request to a first cell of the second base station; and that the handover request is for a wireless device of a first type. At 3420, based on wireless devices of the first type being admitted by the second base station, the first base station may receive from the second base station, a second message comprising a radio resource control (RRC) reconfiguration message. At 3430, the first base station may transmit, to the wireless device, the RRC reconfiguration message.

In an example embodiment, the first type of the wireless device may be a reduced capability wireless device.

In an example embodiment, the first message, transmitted by the first base station to the second base station at 3410, may be a handover request message. The handover request message may comprise one or more information elements indicating that the handover request is for the wireless device of the first type. In an example embodiment, the one or more information elements may comprise a cause information element with a value indicating that the handover request is for the wireless device of the first type. In an example embodiment, the value of the cause information element may indicate that the first base station is offloading wireless devices of the first type to the second base station. In an example embodiment, the value of the cause information element may indicate that a first number of wireless devices of the first type, served by the first base station, reaching a threshold. In an example embodiment, the value of the cause information element may indicate that the first base station is discontinuing serving wireless devices of the first type. In an example embodiment, the one or more information elements may indicate a wireless device identifier indicating that the handover request is for the wireless device of the first type. In an example embodiment, an information element, in the one or more information elements, may take a plurality of values, each value in the plurality of values corresponding to a wireless device type.

In an example embodiment, the second message, received by the first base station from the second base station at 3420, may be a handover request acknowledge message. The handover request acknowledge message may comprise a container comprising a handover command message comprising the RRC reconfiguration message. The RRC reconfiguration message may comprise configuration parameters of the first cell.

In an example embodiment, the first base station may transmit to the wireless device, measurement configuration parameters. The first base station may receive, from the wireless device, measurement information comprising first information associated with the first cell of the second base station. In an example embodiment, a determination of the measurement information, at the wireless device, may be based on the measurement configuration parameters. In an example embodiment, the measurement configuration parameters may comprise parameters for measurement of one or more reference signals. In an example embodiment, the one or more reference signals may comprise at least one of synchronization signal block (SSB) and channel state information reference signal (CSI-RS). In an example embodiment, the first base station may transmit, to the wireless device, first configuration parameters of the one or more reference signals. In an example embodiment, the first configuration parameters may indicate radio resources of the one or more reference signals.

In an example embodiment, the first message (e.g., the handover request message) transmitted by the first base station to the second base station at 3410, may comprise an RRC context (e.g., a handover preparation information message in the RRC context) comprising the one or more information elements. In an example embodiment, the RRC context (e.g., the handover preparation information message of the RRC context) may comprise at least one of the UE-CapabilityRAT-ContainerList, sourceConfig (AS-Config), RRM-Config and AS-Context. The at least one of the UE-CapabilityRAT-ContainerList, sourceconfig (e.g., AS-Config), RRM-Config and AS-Context may comprise the one or more information elements. In an example embodiment, the RRC context (e.g., the handover preparation information message of the RRC context) may comprise a sourceConfig (e.g., AS-Config) IE comprising the one or more information elements. In an example embodiment, the RRC context (e.g., the handover preparation information message of the RRC context) may comprise an AS context IE comprising the one or more information elements.

In an example embodiment, the first message (e.g., the handover request message), transmitted by the first base station to the second base station at 3410, may comprise a mobility restriction list information element comprising the one or more information element.

In an example embodiment, the first message (e.g., the handover request message), transmitted by the first base station to the second base station at 3410, may comprise an information element indicating a global identifier of the first cell of the second base station.

FIG. 35 shows an example flow diagram in accordance with several of various embodiments of the present disclosure. At 3510, a wireless device of a first type may transmit to a first base station, measurement information associated with a first cell of a second base station. At 3520, the wireless device may receive, from the first base station, configuration parameters of the first cell, based on: an indication, from the first base station to the second base station, that the wireless device is of the first type; and wireless devices of the first type being admitted by the second base station. At 3530, the wireless device may transmit to the second base station, a reconfiguration complete message indicating successful completion of a connection reconfiguration.

In an example embodiment, the first type of the wireless device may be a reduced capability wireless device.

In an example embodiment, the wireless device may receive, from the first base station, measurement configuration parameters, wherein the transmitting the measurement information, at 3510, may be based on the measurement configuration parameters.

FIG. 36 shows an example flow diagram in accordance with several of various embodiments of the present disclosure. At 3610, a first base station may transmit to a second base station, a handover request message indicating: a handover request to a first cell of the second base station; and that the handover request is for a wireless device of a first type. At 3620, based on wireless devices of the first type not being admitted by the second base station, the first base station may receive from the second base station, a handover preparation failure message indicating that a handover preparation has failed.

In an example embodiment, the first type of the wireless device may be a reduced capability wireless device.

In an example embodiment, the handover request message, transmitted by the first base station to the second base station at 3610, may comprises one or more information elements indicating that the handover request is for the wireless device of the first type.

In an example embodiment, the handover preparation failure message, received by the first base station from the second base station at 3620, may comprise a cause information element with a first value indicating that wireless devices of the first type is not admitted by the second base station.

In an example embodiment, the handover request message, transmitted by the first base station to the second base station at 3610, may comprise an information element indicating a global identifier of the first cell of the second base station.

In an example embodiment, the first base station may transmit, to the wireless device, measurement configuration parameters. The first base station may receive, from the wireless device, measurement information associated with the first cell of the second base station. In an example embodiment, the measurement information may be based on the measurement configuration parameters. The transmitting the handover request message, by the first base station to the second base station at 3610, may be in response to receiving the measurement information. In an example embodiment, the measurement configuration parameters may comprise parameters for measurement of one or more reference signals. In an example embodiment, the one or more reference signals may comprise at least one of synchronization signal block (SSB) and channel state information reference signal (CSI-RS). In an example embodiment, the first base station may transmit, to the wireless device, first configuration parameters of the one or more reference signals. In an example embodiment, the first configuration parameters may indicate radio resources of the one or more reference signals.

FIG. 37 shows an example flow diagram in accordance with several of various embodiments of the present disclosure. At 3710, a first base station may transmit to a second base station, a secondary node addition request message indicating: a secondary node addition request to allocate resources for dual connectivity operation for a wireless device; and that the secondary node addition request is for a wireless device of a first type. At 3720, based on wireless devices of the first type being admitted by the second base station, the first base station may receive from the second base station, a secondary node addition request acknowledge message. At 3730, the first base station may transmit, to the wireless device, configuration parameters of one or more cells of the second base station.

In an example embodiment, the first type of the wireless device may be a reduced capability wireless device.

In an example embodiment, the secondary node addition request message, transmitted by the first base station to the second base station at 3710, may comprise one or more information elements indicating that the secondary node addition request may be for the wireless device of the first type. In an example embodiment, the one or more information elements may indicate a wireless device identifier indicating that the wireless device is of the first type. In an example embodiment, the secondary node addition request message may comprise a mobility restriction field comprising the one or more information elements. In an example embodiment, the secondary node addition request message may comprise an expected user equipment (UE) behavior field comprising the one or more information elements.

In an example embodiment, the secondary node addition request acknowledge message, transmitted by the second base station to the first base station at 3720, may comprise a cell group configuration information element. The configuration parameters of one or more cells may be based on the cell group configuration information element.

FIG. 38 shows an example flow diagram in accordance with several of various embodiments of the present disclosure. At 3810, a first base station may transmit to a second base station, a secondary node addition request message indicating: a secondary node addition request to allocate resources for dual connectivity operation for a wireless device; and that the secondary node addition request is for a wireless device of a first type. At 3820, based on wireless devices of the first type not being admitted by the second base station, the first base station may receive from the second base station, a secondary node addition request reject message.

In an example embodiment, the first type of the wireless device may be a reduced capability wireless device.

In an example embodiment, the secondary node addition request message, transmitted by the first base station to the second base station at 3810, may comprise one or more information elements indicating that the secondary node addition request is for the wireless device of the first type. In an example embodiment, the one or more information elements may indicate a wireless device identifier indicating that the wireless device is of the first type. In an example embodiment, the secondary node addition request message may comprise a mobility restriction field comprising the one or more information elements. In an example embodiment, the secondary node addition request message may comprise an expected user equipment (UE) behavior field comprising the one or more information elements.

In an example embodiment, the secondary node addition request reject message, received by the first base station from the second base station at 3820, may comprise a cause information element with a first value indicating that wireless devices of the first type is not admitted by the second base station.

FIG. 39 shows an example flow diagram in accordance with several of various embodiments of the present disclosure. At 3910, a first base station may receive from a second base station, an application protocol message comprising one or more information elements indicating first information associated with wireless devices of a first type. At 3920, the first base station may transmit to the second base station, a handover request message based on the first information.

In an example embodiment, the first type of the wireless device may be a reduced capability wireless device.

In an example embodiment, the application protocol message, received by the first base station from the second base station at 3910, may be a setup message (e.g., an Xn setup message, for example, an Xn setup request message or an Xn setup response message).

In an example embodiment, the first information, indicated by the one or more information elements of the application protocol message received by the first base station from the second base station at 3910, may comprise a number of wireless devices of the first type that are served by a cell of the second base station. In an example embodiment, the first information may comprise an indication on whether the second base station serves a wireless device of the first type via a first cell of the second base station.

In an example embodiment, the first information, indicated by the one or more information elements of the application protocol message received by the first base station from the second base station at 3910, may indicate whether the second base station admits wireless devices of the first type. In an example embodiment, the first information may indicate whether the second base station admits wireless devices of the first type on a first cell of the second base station.

In an example embodiment, the first information, indicated by the one or more information elements of the application protocol message received by the first base station from the second base station at 3910, may indicate that the second base station admits wireless devices of the first type on a cell of the second base station. The transmitting the handover request message, by the first base station to the second base station at 3920, may be based on the first information indicating that the second base station admits wireless devices of the first type on the cell of the second base station.

FIG. 40 shows an example flow diagram in accordance with several of various embodiments of the present disclosure. At 4010, a first base station may receive from a second base station, an application protocol message comprising one or more information elements indicating first information associated with wireless devices of a first type. At 4020, the first base station may transmit to the second base station, a secondary node addition request message based on the first information.

In an example embodiment, the first type of the wireless device may be a reduced capability wireless device.

In an example embodiment, the application protocol message, received by the first base station from the second base station at 4010, may be a setup message (e.g., an Xn setup message, for example, an Xn setup request message or an Xn setup response message).

In an example embodiment, the first information, indicated by the one or more information elements of the application protocol message received by the first base station from the second base station at 4010, may comprise a number of wireless devices of the first type that are served by a cell of the second base station. In an example embodiment, the first information may comprise an indication on whether the second base station serves a wireless device of the first type via a first cell of the second base station.

In an example embodiment, the first information, indicated by the one or more information elements of the application protocol message received by the first base station from the second base station at 4010, may indicate whether the second base station admits wireless devices of the first type. In an example embodiment, the first information may indicate whether the second base station admits wireless devices of the first type on a first cell of the second base station.

In an example embodiment, the first information, indicated by the one or more information elements of the application protocol message received by the first base station from the second base station at 4010, may indicate that the second base station admits wireless devices of the first type on a cell of the second base station. The transmitting the secondary node addition request message, by the first base station to the second base station at 4020, may be based on the first information indicating that the second base station admits wireless devices of the first type on the cell of the second base station.

Various exemplary embodiments of the disclosed technology are presented as example implementations and/or practices of the disclosed technology. The exemplary embodiments disclosed herein are not intended to limit the scope. Persons of ordinary skill in the art will appreciate that various changes can be made to the disclosed embodiments without departure from the scope. After studying the exemplary embodiments of the disclosed technology, alternative aspects, features and/or embodiments will become apparent to one of ordinary skill in the art. Without departing from the scope, various elements or features from the exemplary embodiments may be combined to create additional embodiments. The exemplary embodiments are described with reference to the drawings. The figures and the flowcharts that demonstrate the benefits and/or functions of various aspects of the disclosed technology are presented for illustration purposes only. The disclosed technology can be flexibly configured and/or reconfigured such that one or more elements of the disclosed embodiments may be employed in alternative ways. For example, an element may be optionally used in some embodiments or the order of actions listed in a flowchart may be changed without departure from the scope.

An example embodiment of the disclosed technology may be configured to be performed when deemed necessary, for example, based on one or more conditions in a wireless device, a base station, a radio and/or core network configuration, a combination thereof and/or alike. For example, an example embodiment may be performed when the one or more conditions are met. Example one or more conditions may be one or more configurations of the wireless device and/or base station, traffic load and/or type, service type, battery power, a combination of thereof and/or alike. In some scenarios and based on the one or more conditions, one or more features of an example embodiment may be implemented selectively.

In this disclosure, the articles “a” and “an” used before a group of one or more words are to be understood as “at least one” or “one or more” of what the group of the one or more words indicate. The use of the term “may” before a phrase is to be understood as indicating that the phrase is an example of one of a plurality of useful alternatives that may be employed in an embodiment in this disclosure.

In this disclosure, an element may be described using the terms “comprises”, “includes” or “consists of” in combination with a list of one or more components. Using the terms “comprises” or “includes” indicates that the one or more components are not an exhaustive list for the description of the element and do not exclude components other than the one or more components. Using the term “consists of” indicates that the one or more components is a complete list for description of the element. In this disclosure, the term “based on” is intended to mean “based at least in part on”. The term “based on” is not intended to mean “based only on”. In this disclosure, the term “and/or” used in a list of elements indicates any possible combination of the listed elements. For example, “X, Y, and/or Z” indicates X; Y; Z; X and Y; X and Z; Y and Z; or X, Y, and Z.

Some elements in this disclosure may be described by using the term “may” in combination with a plurality of features. For brevity and ease of description, this disclosure may not include all possible permutations of the plurality of features. By using the term “may” in combination with the plurality of features, it is to be understood that all permutations of the plurality of features are being disclosed. For example, by using the term “may” for description of an element with four possible features, the element is being described for all fifteen permutations of the four possible features. The fifteen permutations include one permutation with all four possible features, four permutations with any three features of the four possible features, six permutations with any two features of the four possible features and four permutations with any one feature of the four possible features.

Although mathematically a set may be an empty set, the term set used in this disclosure is a nonempty set. Set B is a subset of set A if every element of set B is in set A. Although mathematically a set has an empty subset, a subset of a set is to be interpreted as a non-empty subset in this disclosure. For example, for set A={subcarrier1, subcarrier2}, the subsets are {subcarrier1}, {subcarrier2} and {subcarrier1, subcarrier2}.

In this disclosure, the phrase “based on” may be used equally with “based at least on” and what follows “based on” or “based at least on” indicates an example of one of plurality of useful alternatives that may be used in an embodiment in this disclosure. The phrase “in response to” may be used equally with “in response at least to” and what follows “in response to” or “in response at least to” indicates an example of one of plurality of useful alternatives that may be used in an embodiment in this disclosure. The phrase “depending on” may be used equally with “depending at least on” and what follows “depending on” or “depending at least on” indicates an example of one of plurality of useful alternatives that may be used in an embodiment in this disclosure. The phrases “employing” and “using” and “employing at least” and “using at least” may be used equally in this in this disclosure and what follows “employing” or “using” or “employing at least” or “using at least” indicates an example of one of plurality of useful alternatives that may be used in an embodiment in this disclosure.

The example embodiments disclosed in this disclosure may be implemented using a modular architecture comprising a plurality of modules. A module may be defined in terms of one or more functions and may be connected to one or more other elements and/or modules. A module may be implemented in hardware, software, firmware, one or more biological elements (e.g., an organic computing device and/or a neurocomputer) and/or a combination thereof and/or alike. Example implementations of a module may be as software code configured to be executed by hardware and/or a modeling and simulation program that may be coupled with hardware. In an example, a module may be implemented using general-purpose or special-purpose processors, digital signal processors (DSPs), microprocessors, microcontrollers, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) and/or alike. The hardware may be programmed using machine language, assembly language, high-level language (e.g., Python, FORTRAN, C, C++ or the like) and/or alike. In an example, the function of a module may be achieved by using a combination of the mentioned implementation methods. 

What is claimed is:
 1. A method comprising: transmitting, by a first base station to a second base station, a secondary node addition request message indicating: a secondary node addition request to allocate resources for dual connectivity operation; and that the secondary node addition request is for a wireless device of a reduced capability type; wherein the reduced capability type is associated with reduced capabilities compared to a non-reduced capability type; receiving, by the first base station from the second base station, a secondary node addition request acknowledge message based on wireless devices of the reduced capability type being admitted by the second base station; and transmitting, by the first base station to the wireless device, configuration parameters of one or more cells of the second base station.
 2. The method of claim 1, wherein the reduced capabilities comprise one or more of: a reduced bandwidth; a reduced number of antennas; and a half-duplex operation.
 3. The method of claim 1, wherein the secondary node addition request message comprises one or more information elements with one or more values indicating that the secondary node addition request is for the wireless device of the reduced capability type.
 4. The method of claim 3, wherein the one or more values comprise a wireless device identifier indicating that the wireless device is of the reduced capability type.
 5. The method of claim 3, wherein the one or more information elements comprise a mobility restriction list information element.
 6. The method of claim 3, wherein the one or more information elements comprise an expected user equipment (UE) behavior information element.
 7. The method of claim 1, wherein: the secondary node addition request acknowledge message comprises a cell group configuration information element; and the configuration parameters of one or more cells are based on the cell group configuration information element.
 8. A method comprising: receiving, by a first base station from a second base station, a secondary node addition request message indicating: a secondary node addition request to allocate resources for dual connectivity operation; and that the secondary node addition request is for a wireless device of a reduced capability type; wherein the reduced capability type is associated with reduced capabilities compared to a non-reduced capability type; transmitting, by the first base station to the second base station, a secondary node addition request reject message based on wireless devices of the reduced capability type not being admitted by the first base station.
 9. The method of claim 8, wherein the reduced capabilities comprise one or more of: a reduced bandwidth; a reduced number of antennas; and a half-duplex operation.
 10. The method of claim 8, wherein the secondary node addition request message comprises a cause value indicating that wireless devices of the reduced capability type are not admitted by the first base station.
 11. The method of claim 8, wherein the secondary node addition request message comprises one or more information elements with one or more values indicating that the secondary node addition request is for the wireless device of the reduced capability type.
 12. The method of claim 11, wherein the one or more values comprise a wireless device identifier indicating that the wireless device is of the reduced capability type.
 13. The method of claim 11, wherein the one or more information elements comprise a mobility restriction list information element.
 14. The method of claim 11, wherein the one or more information elements comprise an expected user equipment (UE) behavior information element.
 15. A system comprising: a first base station comprising: one or more first processors; and first memory storing instructions that, when executed by the one or more first processors, cause the first base station to: transmit, to a second base station, a secondary node addition request message indicating: a secondary node addition request to allocate resources for dual connectivity operation; and that the secondary node addition request is for a wireless device of a reduced capability type; wherein the reduced capability type is associated with reduced capabilities compared to a non-reduced capability type; and receive, from the second base station, a secondary node addition request acknowledge message based on wireless devices of the reduced capability type being admitted by the second base station; and a wireless device comprising: one or more second processors; and second memory storing instructions that, when executed by the one or more second processors, cause the wireless device to: receive, from the first base station, configuration parameters of one or more cells of the second base station.
 16. The system of claim 15, wherein the reduced capabilities comprise one or more of: a reduced bandwidth; a reduced number of antennas; and a half-duplex operation.
 17. The system of claim 15, wherein the secondary node addition request message comprises one or more information elements with one or more values indicating that the secondary node addition request is for the wireless device of the reduced capability type.
 18. The system of claim 17, wherein the one or more values comprise a wireless device identifier indicating that the wireless device is of the reduced capability type.
 19. The system of claim 17, wherein the one or more information elements comprise a mobility restriction list information element.
 20. The system of claim 15, wherein: the secondary node addition request acknowledge message comprises a cell group configuration information element; and the configuration parameters of one or more cells are based on the cell group configuration information element. 